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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is fully covered. The description adds that results include citations, source details, and index status — a hint that output quality depends on indexing state — but does not state access/billing implications or latency expectations. It adds modest context beyond annotations without addressing operational behavior.

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 tight sentences with zero waste: what it does, what it returns, and where to go instead. The core operation is front-loaded and nothing is repeated from the annotations.

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?

Output schema exists, so return-value explanation is not required, and annotations cover safety. However, for a tool with a required nested filters object at 33% schema coverage, the description leaves the agent without guidance on content-type selection, study-count limits, or date scoping — gaps the description should have filled.

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 only 33%: only organization_id is documented in-schema. The description vaguely maps 'selected accessible studies' to filters.study_ids but says nothing about the 20-study cap, the content_types enum, or the research date range filters, which are the substance of the nested object.

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: 'Answer a question across selected accessible studies using indexed research.' It also names the sibling it is not (search_research) and clarifies the scope of the operation, so an agent can distinguish it from search/view siblings without opening any 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?

Explicitly routes the agent to search_research 'to inspect the underlying records,' giving a clear alternative-use condition. It does not address the other plausible alternative (view_research_answer) or state when answering is inappropriate, but the primary routing guidance is present.

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