get_drugs_batch

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

Annotations already declare readOnlyHint=true, and the description does not contradict this. The description adds the batching behavior ('in a single request') but omits details on limits, error handling, or response specifics. It is minimally transparent beyond the annotation.

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 seven words in one sentence, entirely front-loaded and free of filler. It is maximally concise and efficient.

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?

For a simple one-parameter tool with an output schema and readOnly annotation, the description is minimally sufficient for selection but lacks parameter clarification. An agent must infer that chembl_ids refers to ChEMBL identifiers, which is a moderate gap.

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?

The sole parameter chembl_ids is not described in the schema (0% coverage) and the description does not explain that it accepts an array of ChEMBL IDs or any constraints. With low schema coverage, the description should compensate, but it does not.

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 states the tool retrieves multiple drugs in a single request, clearly distinguishing it from single-drug tools like get_drug_info and other batch tools. The verb 'retrieve' and resource 'drugs' are specific and action-oriented.

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 via 'in a single request' but does not explicitly state when to use this tool over alternatives or provide exclusions. Sibling tools like get_drug_info indicate the batch variant, but the description itself offers no direct guidance.

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