get_targets_batch

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

The annotations declare readOnlyHint=true, which already communicates the safety profile. The description adds 'single request' as a behavioral detail, but doesn't disclose other aspects like response size, batching limits, or error behavior. Since annotations cover the main safety concern, this is adequate but not rich.

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 a single, front-loaded sentence with no filler or redundancy. It earns its place by stating the core action and scope, making it as concise as possible.

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 a simple one-parameter tool with an output schema and read-only annotation, so the description doesn't need to explain return values. However, it lacks guidance on batch limits, when to use it over alternatives, and what constitutes a 'target'. The description is minimally sufficient but has clear 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?

Schema description coverage is 0%, so the description must compensate for parameter meaning. It doesn't mention ensembl_ids at all, leaving the agent to infer from the schema property name. The description's 'targets' is less specific than 'Ensembl IDs', failing to clarify what identifiers are expected.

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 'Retrieve multiple targets in a single request' with a specific verb and resource. It distinguishes itself from single-target tools like get_target_info by emphasizing 'multiple' and 'single request', though it doesn't name a sibling alternative.

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 implies batch usage but provides no explicit guidance on when to use this tool versus alternatives. It doesn't mention when not to use it or name a sibling like get_target_info, so the agent receives no clear context for tool selection.

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