Get Diseases (batch)

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

The description adds significant behavioral context beyond annotations, including partial success mechanism (each item returns ok=false/error_code/message), max batch size, and default response mode. No contradiction with readOnlyHint=true or other annotations.

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?

The description is dense and efficient, conveying key information in two sentences plus a signature line. Minor improvement could be structural clarity, but no superfluous content.

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?

The description covers all essential aspects for a batch retrieval tool: partial failure, input constraints, and verbosity options. Without an output schema, it adequately explains the response structure. Could mention error handling for invalid terms.

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 100% schema coverage, the description still adds value by clarifying acceptable input formats for terms (ORPHAcode, label, or xref CURIE), sparse projection via fields, default compact mode, and the signature pattern.

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?

The description clearly states 'Fetch many disease records in one call' with specifics about partial success and per-item structure. It distinguishes itself from sibling tools like get_disease (single record) and resolve_disease_batch by emphasizing batch retrieval with partial failures.

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 description provides clear context for when to use this tool (batch fetching) and includes important constraints (max 50 items, input types). It does not explicitly exclude alternatives but implies its role among siblings.

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