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

Adds substantial context beyond the annotations: it explains the counter-increment side effect that justifies readOnlyHint=false on a 'get' tool, and warns that response strings are sanitized third-party content that must be treated as untrusted data rather than instructions. That is exactly the behavioral guidance annotations cannot convey.

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 compact clauses, front-loaded with the purpose, then the trust warning, then the side effect. Every sentence earns its place with no filler.

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?

No output schema exists, and the description compensates by characterizing the returned content's provenance and trust status plus the side effect of reading. It omits error behavior for missing/expired tokens, which is a minor gap for a single-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?

Schema description coverage is 0% for the single parameter, so the description must carry meaning; it does say the token identifies a shared teardown, but adds no format, validity, or lookup semantics beyond the schema's uuid format. Adequate but thin.

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 (get) and resource (public shared teardown), scoped by share token, which separates it from the corpus/public listing siblings. It does not explicitly contrast with get_public_teardown, so the sibling differentiation is only implicit.

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?

Usage is implied by the required share_token discriminator, but the description never states when to pick this over get_public_teardown or get_corpus_teardown, nor any prerequisites or failure modes for an invalid token.

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