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

Annotations already declare read-only and idempotent, but the description adds real operational context: the return is text with figure captions, up to five concurrent requests are recommended per batch, and a timeout should be retried after waiting. That rate-limit and failure-handling detail is exactly the kind of behavior 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?

Purpose is front-loaded and every sentence carries operational information (availability flag, return contents, fallback, concurrency, retry). The opening sentence is a dense clause pile and could be trimmed, but nothing is redundant.

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?

Despite an output schema existing, the description still tells the agent the shape of the return (text with figure captions) and where to go for deeper verification. Combined with concurrency and retry guidance, an agent has everything needed to call this correctly.

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 100% and the single parameter is documented, so the schema does the heavy lifting. The description still adds provenance the schema lacks — that paper_id comes from search results and that scout_available signals availability — which is useful for correct invocation.

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 ('Read') and a precisely scoped resource: a structured analysis containing signals, methodology, evidence, experimental conditions, verification points and author-stated limitations. The phrase 'beyond the abstract' implicitly separates it from search_papers, and the tied scout_available flag makes the relationship concrete.

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?

Explicit triggers are given ('when these details help assess a candidate, compare findings, or understand the context of a claim'). It also names the fallback path ('consult the original paper through source_url'), how to know the tool applies (scout_available=true in search results), and batching/retry rules for concurrency and timeouts.

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