search_drug_label

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

No annotations are provided, so the description carries the full burden. It only states the basic search action and does not disclose behavioral traits such as default sections searched, pagination behavior, rate limits, or read-only nature. The schema covers some parameter behavior but not the overall tool behavior.

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 a single, front-loaded sentence that efficiently conveys the tool's core purpose. It avoids unnecessary detail or repetition, earning a high score for 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?

Given the tool's moderate complexity (4 parameters, output schema provided), the description is minimal but not fatally incomplete. The schema fills in parameter details, but the description lacks usage context and behavioral transparency, leaving the agent to infer when to use it. It is adequate but has clear gaps.

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 100%, so the baseline is 3. The description adds no additional meaning beyond the term parameter in the schema; it merely mentions 'for a term' without elaborating on syntax, defaults, or section scoping, which the schema already covers.

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 the tool's function: 'Search openFDA drug labels (SPL) for a term.' It uses a specific verb ('Search'), identifies a distinct resource ('openFDA drug labels (SPL)'), and specifies the action ('for a term'). This distinguishes it from sibling tools that focus on applications, devices, or signal screening.

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 no guidance on when to use this tool versus alternatives. It does not mention sibling tools, exclusions, or specific contexts. The purpose is implied but not explicitly contrasted with other tools.

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