batch_bar_aiv_interactions

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

No annotations provided, so description carries full burden. Discloses parallel fan-out, up to 50 loci, shared organism, per-locus result structure, and error handling. Does not mention rate limits or permissions, but adds significant behavioral detail beyond schema.

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?

Two sentences packed with essential information, front-loaded with purpose, no redundant 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?

Given output schema exists, description provides complete behavioral overview: batch nature, limit, organism sharing, per-locus result keys. Covers all necessary aspects for an agent to use the tool effectively.

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% with descriptions for both parameters. Description reinforces max 50 loci and shared organism, and adds context about parallel execution and per-locus result payload. Adds value beyond schema.

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 states 'Batch variant of bar_aiv_interactions' with specific verbs: fans out, parallel, up to 50 loci. Distinguishes from sibling bar_aiv_interactions by specifying batch behavior and per-locus payload structure.

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?

Provides clear usage context: batch multiple loci (1-50) with shared organism. Implicitly suggests use when needing parallel single-locus calls, but does not explicitly exclude other use cases or mention when to prefer the single-locus variant.

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