batch_ensembl_plants_lookup_locus

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

Discloses retry behavior for 429/5xx with capped Retry-After, error handling (NotFoundError in errors[]), and that batch only fails after retry exhaustion. No annotations provided, so description fully carries transparency burden.

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?

Three sentences covering identity, benefit, shape, and error handling. Every sentence adds value, no redundancy.

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?

With output schema present, description covers purpose, behavior, error handling, batch limits, and distinguishes from sibling. No gaps given the tool's complexity and context.

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 100%; description adds minor context (same shape as single-locus) but not significant beyond schema. Baseline 3 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?

Clearly identifies as a batch variant of ensembl_plants_lookup_locus, specifies it uses POST /lookup/id endpoint for up to 50 loci, and distinguishes from the single-locus sibling by highlighting cost savings.

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?

States batch is cheaper for multiple loci due to one round-trip, implying use when loci count > 1. Does not explicitly exclude single-locus use but strongly suggests it via sibling tool existence.

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