get_drug_by_ndc

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

No annotations are provided, so the description carries full burden. It only states 'Get a drug profile' without disclosing any behavioral traits such as read-only nature, authorization requirements, rate limits, or what the output includes. The existence of an output schema might cover return values, but the description itself lacks transparency.

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 and front-loaded with purpose. The 'Args' section is a bit repetitive but acceptable. Every sentence serves a purpose, though the 'Args' section could be integrated more elegantly.

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?

Given the tool's simplicity (one parameter) and presence of an output schema, the description is adequate. It explains when to use and what the parameter is. However, it could enhance completeness by briefly describing what a 'drug profile' contains (e.g., name, dosage, manufacturer) to set expectations.

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 description adds value beyond the input schema by providing an example NDC format ('0363-0160'). However, it does not explain constraints like required format (e.g., digits, hyphen) or any restrictions. With 0% schema description coverage, the description partially compensates but is minimal.

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 action 'Get a drug profile' and the resource 'by its NDC (National Drug Code) package code'. It distinguishes from sibling tools by specifying the input type (NDC vs. name).

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 advises 'Use when you have an NDC from a label or packaging rather than a name', providing clear context for when to use. It does not explicitly state when not to use, but the guidance is sufficient.

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