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 only the vague claim that dossiers 'retain citations/outcomes' plus a pointer to an external guide URI, which is not actionable behavior disclosure. It says nothing about the size or cost of dossier retrieval across seven workflows and twelve nested section types.

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?

It is short, and the inline example earns its place, but the lead sentence about citations/outcomes is cryptic and front-loads the least useful information. The trailing 'biomedmcp://guide' URI is unexplained context that reads as an afterthought.

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?

This is one of the most complex schemas in the sibling set — seven workflow enums, twelve optional section blocks, pagination and threshold sub-parameters — with zero schema description coverage. The description supplies an example and a guide link but leaves an agent unable to choose a workflow or populate section_parameters correctly. An output schema exists, but that only excuses return-value documentation, not the input guidance gap.

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?

With 0% schema description coverage across six parameters (two required, plus a deeply nested DossierParameters object with twelve sub-parameter types), the description must compensate. The single JSON example clarifies 'workflow', 'focus', and 'species' shape, but 'sections', 'section_parameters', 'assembly', and the nested QTL/Civic/Fulltext parameter objects are entirely unexplained.

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?

"Dossiers retain citations/outcomes" and "get further sections" gesture at retrieving dossier content, but the tool is named 'research' and the description never states plainly what operation it performs or what resource it returns. An agent cannot distinguish it confidently from siblings like 'get', 'search', or 'variant_evidence'.

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?

"Inspect capabilities and get further sections for completeness" implies a sequence (call capabilities first, then this tool to fill gaps), but it is framed as an aside rather than explicit when-to-use guidance. No exclusions, prerequisites, or comparison to alternative sibling tools are given.

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