Complete Diagnostic Report

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

Annotations already indicate read-only and idempotent. Description adds details about report contents (odds ratios, evidence levels, bibliography). No contradictions, and provides sufficient behavioral context for a report generation tool.

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?

Description is informative yet reasonably concise. Key information front-loaded ('most comprehensive genomic report'). Could trim excess examples but overall well-structured and earns its length.

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?

Despite no output schema, description details what the report contains (specific numbers: 19 conditions, 30+ traits, all genes, bibliography). Provides complete mental model of tool's output. No gaps.

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?

No parameters; schema coverage is 100%. Description doesn't need to add parameter info. Baseline of 4 for zero-parameter tools is appropriate.

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?

Description clearly states it generates the most comprehensive genomic report by running all modules at once, listing specific components (pharmacogenomics, disease risk, traits). Distinct from siblings that focus on subsets (e.g., full_pgx_report, trait_report).

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 states this is the 'one-click full diagnostic' and user does not need to ask condition by condition, implying it should be used instead of calling individual condition checks. Does not explicitly state when not to use, but context suffices.

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