- Add 'Relationship to Other SEPs' section linking to SEP-1881
  (Scope-Filtered Tool Discovery), SEP-1821 (Dynamic Tool Discovery),
  and SEP-1442 (Make MCP Stateless)
- Replace underscore emphasis with asterisks for consistency
- Remove em dash from capability example
- Replace contractions (don't -> do not)
- Rename title to 'Server Capability Signature' for clarity

- Link to SEP-1862 (Tool Resolution) in related SEPs section
- Add 'Registry Fingerprinting' rationale section explaining how
  signatures enable server identification, change detection, and
  compatibility matching for registries and discovery services
- Add 'Signature and Tool Resolution' section showing how signatures
  can declare all possible tool behaviors upfront via resolvedVariants
- Add open question about whether resolvedVariants should be part of
  the core signature spec
- Update hashing question to mention registry fingerprinting value

- Link to SEP-1913 (Trust and Sensitivity Annotations) in related SEPs
- Clarify that schema freezing either exposes failing tools or fails
  to provide them for everyone
- Fix author name to Sam Morrow

- Document the alternative approach of servers exposing all tools
  and clients filtering based on annotations/scopes
- Explain why this was not chosen (less dynamic, privacy concerns,
  annotation limitations, wasted context, error-prone)
- Note that client-side filtering remains complementary

…g sections

- Add Tadas Antanavicius (PulseMCP) to acknowledgments
- Add SEP-1649 (Server Cards) to related SEPs as primary overlap
- Add major section evaluating Server Cards and InitializeResult as alternatives
- Update Open Questions to include method vs existing mechanism question
- Recommendation to potentially refocus SEP toward Server Card integration

- Major editorial revision reducing length from ~530 to ~385 lines
- Removed redundant sections and trimmed verbose explanations
- Fixed caching approach: HTTP headers (ETag, Cache-Control) for Server Cards
- Removed etag field from ServerSignature (HTTP handles this)
- Fixed worst-case annotation example (destructiveHint: true, readOnlyHint: false)
- Updated SignatureResource to clarify resource vs template type distinction
- Clarified behavioral requirements section
- Improved precision throughout document

Servers can advertise tools that are not yet active but could be enabled,
supporting marketplace integrations, optional features, and tiered service
levels where users choose which tools to activate.