estimate_translation

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

No annotations provided, so description carries full burden. It only states it estimates cost, with no mention of side effects, permissions, rate limits, or other behaviors. Minimal disclosure for a tool that likely requires access to project data.

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 sentences with no fluff. First sentence states purpose, second provides usage guidance. Front-loaded and efficient.

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?

Despite having 8 parameters and 3 required, the description is very brief. It does not explain what the output contains (e.g., cost structure, units) or how to interpret the estimate, leaving gaps for the agent. Incomplete given the tool's complexity.

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 coverage is 50%, description does not add significant meaning beyond the schema. It hints at content types (listing copy, screen text) but does not detail parameters like projectId, fromLanguage, toLanguage, or listingFields. At baseline 3, it provides adequate but not enhanced semantics.

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 it estimates AI credit cost for translation of listing copy and/or screen text. It distinguishes from siblings by specifying 'before translate_project', implying a unique role.

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?

Explicitly instructs to always call before translate_project when credits matter, providing clear when-to-use guidance. Lacks explicit when-not-to-use or alternatives, but the instruction is direct.

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