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

Annotations already declare readOnlyHint=true, destructiveHint=false, and a closed-world scope, so the safety profile is covered. The description adds one behavioral fact not in annotations — the return shape, 'a formatted table' — which is useful given there is no output schema, but it omits pagination/ordering 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?

Two short sentences, no filler, and the scope constraint is front-loaded. The second sentence, disclosing the return format, earns its place since there is no output schema.

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 simple single-param list tool with annotations covering safety and a description noting the return format, this is largely sufficient. The only gap is the absence of any hint about ordering or empty-result behavior, which is minor here.

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 100% and the single researchId parameter is fully documented in the schema. The description's 'for a specific research' simply restates the schema's meaning without adding format, constraints, or examples, so the baseline 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?

States a clear verb (List), resource (deep dives), and scope (for a specific research), which separates it from the singular get_deep_dive sibling. It does not explicitly name or contrast against a sibling, so it stops short of the top band.

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?

There is an implicit condition — you must have a specific research in hand — but no explicit when-to-use, when-not-to-use, or guidance distinguishing this from get_deep_dive (single) or the other list_* tools. The agent is left to infer the routing.

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