translate_pass_text

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

Annotations already declare readOnlyHint=true, so the tool is known to be safe. The description adds context by naming the external service (Google Cloud Translation) and noting language coverage. It doesn't disclose rate limits or return format, but these are not critical for a read-only translation operation.

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, front-loaded with the action and purpose, and no wasted words. Every sentence contributes to the agent's understanding.

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?

For a simple tool with three primitive parameters and no output schema, the description covers purpose, usage, and the external service. It lacks an explicit return format, but that can be inferred from typical translation tools and the read-only annotation.

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 each parameter is described. The description reinforces the meaning of the parameters (e.g., 'texts' are pass content strings) without adding new syntax or edge-case details. This meets the baseline for full schema coverage.

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?

States a specific action ('Translate'), the resource ('pass text'), the method ('Google Cloud Translation'), and the purpose ('localize pass content for international customers'). Clearly distinguishes from sibling tools that create or update passes.

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 states when to use ('to localize pass content') and implies the context of internationalization. It doesn't mention alternatives or exclusions, but since no other translation tool exists among siblings, the guidance is adequate.

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