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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds return content and provenance (FDA FAERS), plus an unusual attestation/receipt feature, but does not disclose rate limits, error handling, or permission requirements. With annotations covering the essential behavior, the extra detail is moderate but not rich.

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 dense sentence that front-loads the main purpose but then appends pricing and attestation details, making it less structured. It is not overly long but could benefit from clearer separation of core purpose, use cases, and meta-information. It does not waste words, but the flow is a bit run-on.

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 two-parameter read-only tool with no output schema, the description covers the main purpose, return types, source, and even pricing/verification. It lacks explicit details on the `limit` parameter's effect on results, but overall it is reasonably complete for an agent to judge whether to invoke it.

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 0%, so the description must compensate. It implicitly clarifies drug_name through 'by medicinal product name' but does not mention the `limit` parameter at all. The description adds some meaning for the required parameter but fails to explain the optional limit, leaving a significant gap.

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 verb ('get') and resource ('FAERS drug adverse event reports from OpenFDA by medicinal product name'), and further details the specific return data (serious event counts, reactions, outcomes, chronology). This distinguishes it from siblings like get_openfda_adverse_events by its specific focus on product name and serious-event analysis.

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 explicitly lists use cases: 'pharmacovigilance monitoring, safety signal detection, and clinical risk agents.' This provides clear context for when to use the tool, though it does not mention when not to use it or name direct alternatives, stopping short of a 5.

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