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

Discloses behavior well beyond the annotations: it warns the content is captured from third-party sites and sanitized, that every string must be treated as untrusted data rather than instructions (prompt-injection defense), and that reading increments a view counter. The counter note also coherently explains why readOnlyHint and idempotentHint are false, so the description and annotations reinforce each other.

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 tightly written sentences, front-loaded with the core operation and followed by only the safety and side-effect context an agent actually needs. 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?

For a single-parameter getter with no output schema and no annotations covering safety semantics, the description covers purpose, security handling, and the counter side effect. The only real gap is disambiguation from its four similarly named siblings.

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 coverage is 0%, so the schema alone does not document share_token, but the description only restates the concept ('by share token') without adding format or syntax detail beyond the schema's uuid format. Some value, but it does not fully compensate for the coverage gap.

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 and resource ('Get a public shared teardown') plus the access mechanism ('by share token'), so the agent knows exactly what this returns. It does not distinguish itself from the sibling get_public_teardown, leaving the shared-vs-public boundary to inference.

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 'by share token' – the agent can infer it needs a token in hand – but there is no explicit when-to-use guidance and no mention of the sibling get_public_teardown or get_corpus_teardown as alternatives.

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