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

Annotations already declare readOnly, non-destructive, idempotent and closed-world; the description adds real value on top by confirming no provider contact/no cost and disclosing that unknown schemas are marked rather than silently omitted. It stops short of describing return structure for known tools.

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?

Three short, front-loaded sentences with zero filler; the core read action comes first, then the cost/safety note, then the edge-case behavior.

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 no output schema, the description usefully enumerates the returned content (metadata, parameters, pricing, JSON example) and flags the unknown-schema case. Only the tool-identifier format and any size/rate limits are unaddressed, which is minor for a one-parameter read.

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?

One required 'tool' parameter with 0% schema description coverage, yet the description never says how a tool is identified (name, id, slug) or how unknown tools are handled. 'Unknown input schemas are explicitly marked' hints at output rather than input semantics.

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?

States a specific verb+resource: reading local tool metadata (parameters, pricing, request example). The word 'local' plus 'does not contact a provider' implicitly separates it from run_tool, though no sibling is named explicitly.

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?

'Free; does not contact a provider' implies inspection-before-execution usage, but there is no explicit when-to-use vs search_tools/get_run/run_tool guidance or exclusion statement. Usage is inferable rather than stated.

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