get_dosage_form

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

With no annotations, the description carries the full burden. It adds useful behavioral context by defining dosage form and noting that a product can have multiple forms when it is a kit. However, it does not mention default behaviors of parameters like active_only, return format, or error cases.

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 two clear sentences. The first sentence states the action and target, the second provides a concise definition and a valuable caveat about kits. No wasted words and information is front-loaded.

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 simple lookup nature, an output schema exists, and the input schema covers all parameters well, the description is largely complete. It lacks explicit usage guidance relative to siblings, but that is already scored separately. It provides enough context for an agent to understand the tool's role.

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 provides detailed descriptions for all 4 parameters, including enums and defaults (100% coverage). The description does not add parameter-level meaning beyond referencing drug product, so baseline score of 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 uses specific verb 'Get' plus resource 'dosage form(s) for a drug product'. It also clarifies the domain concept with examples and notes the special case of kits, making it clearly distinct from sibling tools like get_route_of_administration or get_drug_product.

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 this is for retrieving dosage form information for a specific drug product, but it does not explicitly state when to use this tool versus alternatives like get_all_drug_info or get_route_of_administration. No exclusions or alternative guidance is provided.

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