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

Annotations already cover the safety profile (readOnly, openWorld, idempotent, non-destructive), so the description's contribution is the cost model: free within the daily allowance, then $0.003 USDC per call via x402. That is genuinely useful behavioral context an agent needs for cost-aware routing, though auth/quota specifics remain unstated.

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?

Two short, front-loaded sentences with zero waste: the resource identity comes first and the pricing caveat second. Every sentence carries distinct information.

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 an output schema present, return values need no description, and the two params are fully covered by the schema. The description adds the source database and cost model, but omits how to construct a valid openFDA search expression, which would help an agent avoid failed calls.

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 schema already documents both parameters (search expression, limit default/max). The description adds no syntax or format detail for the search expression, so the baseline 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 identifies the specific resource: MAUDE medical device adverse event reports, which is distinctive enough to distinguish it from openfda__device-recalls and openfda__drug-adverse-events. However, it is a noun phrase with no explicit verb (search/query/fetch), leaving the action to be inferred from the schema.

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?

There is no guidance on when to use this tool versus its many siblings (device-510k, device-recalls, drug-adverse-events), nor any prerequisites or context. Usage must be inferred entirely from the resource name.

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