biothings_query_many_chems

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

No annotations are provided, so the description carries full burden. It discloses the batch nature and supported queries but lacks mention of behavioral traits like whether it is read-only, authentication needs, rate limits, or error handling. The description is insufficient for full transparency.

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 reasonably concise and front-loads the purpose. It uses bullet points for structure, though some text could be tightened. Overall, it is efficient and well-organized.

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 the tool's complexity (4 parameters) and presence of an output schema, the description covers the key aspects: batch query, supported query types, parameter usage. It does not discuss errors or output details, but the output schema exists to fill that gap. It is complete enough for a query tool.

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. It explains the main parameter 'query_list' with examples, and describes 'scopes' and 'fields' with usage context. Only the 'email' parameter is not discussed. This adds significant meaning beyond the 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?

The description clearly states it performs batch queries of chemical compounds by multiple terms, with examples. It distinguishes from siblings like biothings_get_chem and biothings_query_chems by explicitly mentioning 'batch' and 'multiple terms', but could more directly contrast with those tools.

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 provides supported usage scenarios (multiple query types, field scoping, result filtering) but does not explicitly state when to use this tool versus alternatives or when not to use it. The usage guidance is implied through examples.

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