fda_drug_labels

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

Annotations already declare readOnlyHint=true. Description adds that it is searchable and mentions count fields, but does not disclose additional behavioral traits such as rate limits, pagination behavior (beyond limit parameter), or authentication requirements. It adds some value but not substantial beyond annotations.

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 concise, front-loading the purpose and including multiple relevant examples in a structured format. Every sentence adds value, and the list of contained content and count fields is efficient.

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?

Despite no output schema, the description implies the search returns labeling content and lists included fields. However, it does not specify exact return structure, potential formats, or note result limitations beyond a max of 100. Adequate for a search tool but could be more complete.

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?

With 100% schema coverage, baseline is 3. The description adds query syntax examples and explains the limit parameter's default and maximum, going beyond the schema's type and description. This practical guidance aids parameter understanding.

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 tool searches FDA drug product labeling (package inserts/prescribing information) and lists included content (indications, warnings, etc.). It distinguishes from siblings by specifying SPL/labeling content, which is distinct from other FDA drug tools like fda_approved_drugs or fda_drug_events.

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 provides search examples but does not explicitly state when to use this tool versus alternatives like fda_approved_drugs or fda_drug_events. While examples imply usage for labeling searches, no direct guidance on when not to use it or clear differentiation.

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