Resolve Diseases (batch)

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint. Description adds that the call never fails wholesale and each item returns its own success/failure, which is valuable behavioral context beyond 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?

Description is very concise (three sentences), front-loaded with the core action, and includes essential constraints (max 50, partial success, response structure). No unnecessary words.

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 batch tool with output schema, the description covers batch nature, partial success, size limit, and per-item response format. It does not explain the output schema fields, but that is provided separately. Minor gap: no guidance on when to use which response_mode.

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 coverage is 100%, so baseline is 3. Description adds the array length constraint '1..50' and a signature hint, but does not significantly deepen understanding beyond what the schema provides.

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 uses specific verb 'resolve' and resource 'many labels/ORPHAcodes/xrefs in one call', clearly distinguishing it from the single-item sibling 'resolve_disease'. It also clarifies the partial success behavior.

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?

Description states when to use (batch resolution, max 50 items) and mentions partial success, but does not explicitly exclude cases where a single resolution would suffice. The sibling list provides context for alternatives.

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