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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds that the payload includes editorial status and curated trials (implying non-exhaustive, editorially filtered content), but says nothing about size, caching, or failure behavior when a domain id is unknown.

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 dense sentences with the payload contents front-loaded and the follow-up actions clearly separated. No filler, though the all-caps phrasing and list packing make it slightly harder to scan than plain prose.

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 return values need not be explained, and the description nonetheless previews the dossier's sections. For a single-param read tool with annotations and an output schema, the only real gap is sibling disambiguation.

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 one parameter at 100% schema coverage, the schema already documents the id fully. The description only echoes 'the same domain id', adding no format or constraint detail beyond the schema. Baseline 3 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?

Uses a specific verb and resource ('GET ONE DISEASE DOSSIER') and enumerates exactly what the dossier contains (therapies with evidence tiers, biomarkers, trials, red flags), which distinguishes it from narrower siblings like get_disease_drugs or get_disease_targets. Slight ambiguity: the name says 'disease' while the parameter is a domain id ('endocrinology'), so the agent must reconcile that itself.

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 'NEXT:' clause routes to get_disease_targets, search_literature and search_datasets with the same domain id, which is useful forward guidance. However it never states when NOT to use this tool or why to pick it over compare_diseases, get_disease_targets, or explore_condition_registry, so selection logic is only implied.

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