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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), so the bar is lower, and the description adds genuinely non-structured behavior: a per-call charge of $0.005 USDC via x402. It also discloses what data categories come back. It does not say what happens for an unknown drug name or whether multiple brand/generic matches are returned.

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 tightly packed sentence: purpose and source first, then the returned content, then the cost caveat. No filler, no redundancy, and the paid-call detail is placed last where it does not obstruct selection.

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?

With no output schema, the description carries the burden of describing returns, and it does so by listing label sections, side effects and recalls. The x402 payment cost is also disclosed. Only edge-case behavior (no match, partial data, rate limits) is left unstated.

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?

There is one parameter with 100% schema description coverage, and the schema already documents it as 'Brand or generic name'. The description repeats essentially the same phrase, adding no new syntax, format, or matching semantics, so the baseline of 3 applies.

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 names a specific resource and source ('Drug information from openFDA') and enumerates the exact payload (label sections, side effects, recalls), so the agent knows precisely what it gets. It does not, however, differentiate itself from the sibling 'recalls' tool, which overlaps on the recalls portion, so it falls short of the top band.

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?

Usage is only implied: the enumeration of label fields, side effects and recalls signals when an agent would want it, and 'for a brand or generic drug name' hints at the accepted input. There is no explicit 'use this instead of X' or when-not guidance, and the overlap with the 'recalls' sibling is left unresolved.

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