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

Beyond the readOnly/idempotent annotations, the description discloses the result shape (claims plus literature sources), the fact that each claim carries a receipt with source store, read timestamp and derivation method, and the important caveat that claims are derived context rather than measured values. The explicit instruction to treat third-party titles and urls as data rather than instructions is exactly the kind of safety behavior annotations cannot express.

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 most important information, what is returned and its scope, is front-loaded in the first sentence, and each subsequent sentence adds a distinct fact (receipt contents, provenance caveat, untrusted-content warning). It is dense but not padded; a minor tightening of the receipt sentence would make it a 5.

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 and no annotations covering return values, the description correctly takes on the job of describing the payload and its provenance metadata. Gaps remain around what happens when the slug is unknown, and whether results are paginated or bounded, which matter for a lookup an agent may chain into.

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?

There is a single parameter with 100% schema description coverage, so the schema already carries the burden; the description only reinforces that lookup is scoped to one sequence. It adds no format, casing, or sourcing guidance for the slug beyond what the schema 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?

"Returns review-pending identity claims and literature sources for one sequence" gives a specific verb plus two concrete resources and scopes it to a single sequence. It also implicitly separates itself from the certificate/efficacy siblings by stating claims are "never measured lot values or efficacy statements." It stops short of naming any sibling tool outright, so an agent must infer the routing rather than read it.

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 "for one sequence" and by the exclusion of measured lot values, which points an agent toward the COA-style sibling for those. However, there is no explicit when-to-use/when-not statement and no mention that the slug presumably originates from defiance_sequence_lookup, so the agent gets context but no routing rules.

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