get_pharmaceutical_standard

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only defines 'pharmaceutical standard' and does not mention permissions, error behavior, or response details. The 'get' verb implies read-only, but no explicit safety or side-effect context is given.

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, two sentences, with the action front-loaded. The second sentence provides useful definitional context without unnecessary fluff, making it appropriately sized and 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 simple getter, the description is minimally viable but lacks comprehensive guidance: it does not discuss usage scenarios, behavioral caveats, or response handling, though an output schema exists. The gaps in usage guidelines and transparency keep it from being fully 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?

The input schema already describes both parameters (drug_code and type) with 100% coverage. The description adds no additional parameter-specific meaning beyond clarifying what a pharmaceutical standard is, which indirectly relates to the drug_code parameter but is already evident from the schema.

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 gets a pharmaceutical standard for a drug product, using a specific verb and resource. This distinguishes it from sibling tools like get_active_ingredients or get_dosage_form, making the purpose unambiguous.

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 the tool is used when you need the pharmaceutical standard for a drug product, but it gives no explicit guidance on when to use it versus alternative tools, nor does it mention any exclusions or prerequisites. The context is clear but no alternatives are discussed.

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