get_drug_dosage

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

The description adds a behavioral contract instructing agents to treat structuredContent as source of truth and preserve metadata fields, which goes beyond basic purpose. However, with no annotations, it omits other traits like idempotency or side effects.

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?

Two concise sentences front-load the purpose and then add a critical behavioral contract. No redundant words; every sentence earns its place.

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 existence of an output schema and multiple siblings, the description covers the core purpose and a key behavioral rule. It could mention when drug_name must be exact or error handling, but it is sufficient for an agent to use the tool safely.

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?

Schema description coverage is 67% (two of three parameters have descriptions). The tool description does not add meaning to the undocumented drug_name parameter and only indirectly relates to locale/output_format via the contract. No param-specific elaboration.

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 'Get dosage and administration information for a drug,' which is a specific verb-resource pair. It distinguishes the tool from siblings like get_drug_info or get_drug_warnings by focusing on dosage and administration.

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 'Agent contract' provides behavioral instructions but does not explicitly state when to use this tool vs alternatives like get_drug_info. There is no guidance on when not to use it or prerequisites, leaving the agent to infer context from the tool name.

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