Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover readOnly, idempotent, and non-destructive behavior. The description adds 'deterministic' and 'signed' attributes, which slightly extends the behavioral picture by indicating reproducible, cryptographically signed results. However, it does not disclose what input boundaries exist or what 'assessment' actually entails beyond that.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is one sentence and wastes no words. Front-loading the name and appending the key behavioral qualifier is efficient. It is concise, though the brevity contributes to vagueness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With two required parameters and no enums, the tool is moderately simple, but the description leaves essential details undefined: what protocol versions are valid, how methods should be passed, what a 'signed assessment' looks like, and how the result should be consumed. The output schema mitigates return-value ambiguity, but input semantics and operational meaning are missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema names required parameters (protocol_version, methods) but gives no property descriptions Armstrong. The description's 'supplied input' adds no meaning to these parameters. Although schema description coverage is reported as 100%, the visible schema lacks any property-level documentation, so the description does not compensate for the missing semantic context around protocol_version or methods.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description, 'deterministic signed assessment over supplied input,' restates the name's 'compatibility gateway' without explaining what compatibility is being assessed or what the output represents. There is no clear verb-resource pair—'assessment' is generic and does not distinguish this from numerous sibling assessment/gateway tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is given about when to use this tool versus alternatives. None of the sibling tools (e.g., mcp_manifest_firewall, preflight, verify) are referenced, and no context or exclusions are provided, leaving an agent with no basis for routing between similar tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.