ai.translate

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

The description reveals one behavioral trait: source language auto-detection if omitted. However, since there are no annotations, the description carries the full burden of disclosing behaviors. It does not mention rate limits, auth needs, supported languages, text length limits beyond schema, or what happens on failure.

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 extremely concise: two short sentences that front-load the core purpose. Every word adds value without redundancy.

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?

The description is incomplete for a tool with no output schema. It does not state what the tool returns (e.g., the translated text). It also lacks details on error conditions, supported language codes, or text length considerations beyond the schema's maxLength.

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% (targetLanguage and sourceLanguage have descriptions, text does not). The description adds minimal new info: it clarifies that sourceLanguage is auto-detected if omitted, which repeats the schema description for that parameter. The text parameter lacks any description in both schema and tool description.

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's purpose: 'Translate text into a target language.' It uses a specific verb ('Translate') and resource ('text') and distinguishes itself from sibling tools like ai.describe-image, ai.extract, ai.screenshot, and ai.summarize, which have different functions.

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 provides no explicit guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or conditions. It simply states the function, leaving the agent to infer the context.

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