translate_drug_name

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

No annotations provided, so description bears full burden. It discloses reliance on local mapping data (implying limited availability) and includes behavioral contract about preserving structuredContent and not inferring clinical facts. This adds useful context for an agent.

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?

Description is two sentences: one clear statement of purpose and one concise agent contract. Front-loaded with key information, no extraneous words.

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?

With an output schema present, description adequately covers purpose and behavioral rules. Could mention error handling if mapping unavailable, but overall sufficient for a simple translation tool.

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% with only locale and output_format having descriptions. The tool description does not add any additional parameter meaning beyond the schema, and the required 'name' parameter lacks any description in both schema and description, leaving ambiguity.

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?

Description clearly states the tool translates drug names between English and Traditional Chinese using local mapping data. It specifies verb 'translate', resource 'drug names', and language pair, distinguishing it from sibling tools like search_drug or get_drug_info which do not perform translation.

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?

Agent contract provides explicit instructions on handling output (preserve fields, don't infer missing facts), guiding when to use this tool and how to process results. However, no explicit when-not-to-use or alternative tools are mentioned.

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