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

With no annotations, the description carries the full burden. It discloses the sorting order (newest-first), pagination (cursor, up to 1000/page), filtering options, and pricing ($0.05/row). It also notes the data is observational and not a clinical recommendation. However, it does not mention rate limits, authentication requirements, or whether the tool is read-only.

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 front-loaded with an engaging question, then clearly states the purpose and capabilities. While not extremely concise, every sentence adds value. The pricing is noted at the end. It could be slightly shorter but is well-structured.

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 feed tool with 6 optional parameters and no output schema, the description lists the output fields (sponsor, application number/type, brand names, etc.), explains pagination and filtering, and mentions pricing. It provides sufficient context for an agent to understand what the tool returns and how to use 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?

The input schema has 100% description coverage, so each parameter is already documented. The tool description reiterates the filterable fields and adds enum values for submission_type (ORIG/SUPPL), but does not add significant new meaning beyond the schema. Baseline 3 is appropriate.

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 it is a bulk feed over openFDA Drugs@FDA approvals, sorted newest-first by approval date. It specifies the resource (FDA approvals) and the action (bulk feed with cursor pagination). This distinguishes it from sibling tools like fda_approvals_drugs (search) and fda_feed_clearances (devices).

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 implies usage for obtaining recent approvals in bulk, but does not explicitly state when to use this tool versus alternatives like fda_approvals_drugs or fda_feed_clearances. It provides context for pagination and filtering but lacks direct comparison or exclusion criteria.

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