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

Annotations already declare readOnlyHint=true, so the safety profile is covered by structured data. The description adds the semantic content of the dataset (injuries, deaths, malfunctions) and the underlying endpoint, but says nothing about rate limits, pagination ceilings, or result shape beyond what the schema implies.

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 fragments with the substantive content (dataset and subject matter) front-loaded and no filler. The trailing 'openFDA device/event endpoint' is mildly redundant but is genuinely useful for mapping to the API docs.

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 should ideally hint at return format or result interpretation, and it does not. Parameters are exhaustively covered by the schema and read-only safety is covered by annotations, so the tool is callable, but the description leaves gaps around output behavior.

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 skip/sort/limit/search are already fully documented, including Lucene syntax and range examples. The description contributes no additional parameter meaning, which matches the baseline 3 when the schema does all the work.

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?

States a specific verb ('Search') plus the exact resource ('MAUDE database: medical device adverse events — injuries, deaths, malfunctions') and names the underlying endpoint. An agent can distinguish this from siblings like search_device_recalls or search_drug_events purely from the resource scope.

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 identifies what dataset it queries but never states when to choose it over alternatives such as count or openfda_query, nor does it mention prerequisites, expected use cases, or exclusions. Usage is only implied by the resource name.

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