translate_excel

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

No annotations are provided, so the description carries the full burden. It states that the tool preserves formatting, formulas, images, and charts, and that the response contains base64-encoded data. This provides useful behavioral context beyond the schema.

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 excessively long and includes imperative instructions for the AI agent (e.g., 'DO THIS AUTOMATICALLY', 'DO NOT ask for permission'). These are not typical tool usage instructions and add verbosity. The core purpose is buried in procedural details.

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 complexity (7 parameters, no output schema), the description covers file handling, languages, and expected output. It explains how to provide the file and what the response looks like. However, it lacks error scenarios or behavior when conflicts arise (e.g., both file_path and file_content_base64 provided).

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 100%, so baseline is 3. The description adds context for the 'file_content_base64' and 'file_path' parameters, explaining when to use each. It also clarifies the 'context' parameter and provides a workflow. This adds value beyond the schema.

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 translates Excel files and preserves formatting, formulas, images, and charts. It distinguishes from siblings like translate_texts by focusing on Excel. However, the inclusion of automatic behavior instructions slightly blurs the core purpose.

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 explicitly specifies when to use the tool: when a user uploads a file and asks to translate. It provides a step-by-step process. It does not mention when not to use it or alternative tools, but sibling tools are listed for context.

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