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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: the output is generated statements with numbered citations tied to canonical content IDs, plus source details and index status. It does not mention latency, cost, or what happens if the index is stale.

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 packed sentences that front-load what the tool returns and end with the sibling routing. 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?

An output schema exists, so the description needn't enumerate return fields, yet it still summarizes them usefully. The main shortfall is the unaddressed filter parameters and index-readiness prerequisites for a tool with a nested required object.

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 only 33%, and the description never mentions the filters object fields (content_types, research_date_from/to) or the 20-study cap. 'Selected accessible studies' hints at the study_ids filter, but the nested filter semantics and valid content types are left entirely to the schema, so the description only marginally compensates 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 (answer), resource (question across selected studies), and mechanism (indexed research), then distinguishes itself from search_research by naming what it does differently (inspect underlying records). An agent can pick between the two without opening a schema.

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?

The final sentence explicitly routes the agent to search_research for inspecting raw records, giving a clear alternative. However, it doesn't say when NOT to use this tool (e.g. no accessible studies, index not ready) or what prerequisites like an existing index imply.

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