Translate text (Zoom Translator)

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

Discloses the automatic splitting behavior for long texts, which is important. However, with no annotations, the description should also cover authentication, rate limits, and error handling, which are absent. The split detail is valuable but not comprehensive.

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, zero waste. First sentence states purpose, second adds critical behavioral detail. Efficient and well-structured.

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 annotations and no output schema, the description covers purpose and a key behavior (splitting). However, it does not describe the return format, error handling, or prerequisites. Slightly incomplete for a simple tool, but adequate.

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 the baseline is 3. The description adds context about the character limit and splitting, but does not enhance per-parameter meaning beyond what the schema provides (text, source, target). Adequate but not extra.

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 text between languages using a specific API. It also mentions automatic splitting for long texts, which is a key detail. The tool's purpose is distinct from siblings summarize_transcript and transcribe_audio, making it unambiguous.

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?

No explicit guidance on when to use this tool versus alternatives. The purpose is clear, but the description does not provide usage context or contrast with siblings. Implied usage from the tool name and siblings, but no explicit when-not-to-use.

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