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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered by structured data. The description adds that the payload includes 'scope caveats' and 'next actions', which hints at limitations being disclosed inside the response, but it does not say what those caveats are or how large the manifest is. Additional transparency is modest, not rich.

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?

Two sentences, front-loaded with what the tool is, followed by the when-to-use and the alternative. The middle section is a long comma-delimited inventory of sections ('vocabulary guard, scope caveats, next actions, and contact') that verges on listy, but every element is arguably meaningful to an agent deciding whether to call.

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?

This is a low-complexity, zero-required-parameter orientation tool with an output schema, so the description need not explain return values. It covers purpose, trigger, and sibling routing, which is most of what an agent needs. The only gap is that a reader cannot tell how much content each 'detail' mode yields.

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?

Schema description coverage is 100% and the single 'detail' enum is documented in-schema, including when to pick routing or examples. The description mentions the sections (routing table, examples) but adds no syntax or format detail beyond what the schema already states, so the baseline 3 applies.

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 names the resource precisely (a compact capability manifest for clients) and enumerates what it contains, so an agent knows it is an orientation/onboarding tool rather than a data query. It distinguishes itself from 'coverage' by assigning coverage facts to that sibling. The verb is implicit ('this is a manifest' rather than 'returns a manifest'), and internal jargon like 'vocabulary guard' is opaque, which keeps it off a 5.

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?

'Use when new or context is tight' gives an explicit trigger condition, and 'call coverage for coverage facts' names the alternative and the condition that routes away from this tool. It does not enumerate when-not-to-use beyond that single routing case, but the key selection decision is stated outright.

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