drug_search

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the search scope but not additional behavioral context such as result ordering, pagination behavior, or open-world matching caveats.

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?

A single, front-loaded sentence states the verb, resource, and search dimensions with no filler or redundancy. Every word contributes.

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 read-only search tool, the combination of description, input schema, and annotations gives an agent enough to invoke it correctly. The lack of an output schema means return format is not explicit, but the search semantics are clear.

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 schema already describes query as 'Drug name, mechanism, or keyword to search' and documents limit and offset defaults/ranges, so high schema coverage carries the parameter burden. The description essentially restates the query meaning without adding new parameter detail.

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 uses a specific verb ('Search') and resource ('drugs') and names the search dimensions (name, mechanism, keyword), making the tool's purpose clear. It does not explicitly contrast with sibling search tools, but the drug resource is unambiguous.

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 use for drug-related keyword searches, which is sufficient context. It does not state when to prefer this tool over an alternative or list exclusions, though sibling names suggest this is the only drug-specific search.

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