estimate_translation_cost

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

Even without annotations, the description fully discloses behavior: it returns estimates (not actual translations), explains constraints on input, and includes privacy guidance (not showing base64). No side effects or destructive actions are implied, which is appropriate for a read-only estimation tool.

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 front-loaded with purpose and returns, then organized with numbered usage instructions and an important note. Every sentence adds value without redundancy. Despite moderate length, information density is high.

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 no output schema or annotations, the description covers all essential aspects: what the tool does, what inputs are needed, how to use each input modality, and what output to expect. It provides complete guidance for an AI agent to select and invoke the tool correctly.

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?

All three parameters are described in the schema (100% coverage) and the description adds meaningful context: 'file_path' for local files, 'file_content_base64' for base64 input, 'sheets' for filtering. It also clarifies mutual exclusivity of the file parameters.

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 estimates translation cost for an Excel file and lists specific return values (cell count, API cost, processing time). It is distinct from sibling tools like 'translate_excel' (which performs translation) and 'count_translatable_cells' (which counts cells without cost estimation).

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?

Provides explicit instructions for different input types (local file path, uploaded file, base64), warns against providing both file_path and file_content_base64, and advises not to show base64 content to the user. This gives clear when-to-use guidance and prevents misuse.

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