Batch: ATTED-II Coexpression

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

Description adds specific behavioral constraint (up to 50 loci per call) beyond annotations. Annotations already declare readOnly, idempotent, and non-destructive, so minimal additional disclosure needed.

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?

Extremely concise single sentence, front-loaded with key information. Could include slightly more detail without harming conciseness.

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?

Adequate for a simple batch tool with output schema present. Minimal description but sufficient given the tool's straightforward nature and rich annotations.

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?

Description provides no parameter information. Schema coverage is only 33% (organism described), and the description does not compensate for the missing parameter semantics for loci and top_n.

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?

Explicitly states it is the batch version of atted_coexpression, with a clear limit of 50 loci per call. This distinguishes it from the single-locus sibling tool.

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?

Implies usage for batch coexpression queries with multiple loci. Does not explicitly state when not to use or mention alternatives, but the 'batch' prefix in name and description provides clear context.

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