translate-toolTranslate the given text using the translator specified and return the result.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | The translator to use. Supply the translator slug. | |
| text | No | The text to translate. |
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | Input Text | |
| translated | Yes | Translated Text | |
| translator | Yes | Translator used |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and idempotentHint=true, covering the safety and repeatability profile. The description adds no additional behavioral context beyond the trivial 'return the result'—no error handling, slug validation, or side-effect details. Since no extra transparency is provided beyond the annotations, a low score is warranted.
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 a single concise sentence that front-loads the action and result. No filler or redundant information. It earns its place efficiently.
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 tool with only two parameters, a provided output schema, and clear annotations, the description covers the basic contract. However, it omits a hint that valid translator slugs might need to be discovered (e.g., via list-all-translations-tool) and does not specify behavior for missing text or invalid slug. Given the low complexity, the description is mostly complete but could be slightly stronger.
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?
The input schema has 100% description coverage: slug is described as 'The translator to use. Supply the translator slug.' and text as 'The text to translate.' The description merely restates these concepts ('translator specified', 'given text') without adding meaning beyond the schema. Baseline 3 is appropriate.
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 action ('Translate'), the object ('given text'), and the mechanism ('using the translator specified'), and implies a result is returned. It is distinguishable from the sibling list-all-translations-tool, which lists translations rather than performing them, though it does not explicitly reference the sibling.
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 guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. The existence of sibling list-all-translations-tool is not leveraged to direct the agent when to translate versus list. Usage is only implied by the tool's name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
The two tools have clearly distinct purposes: one lists available translators, the other performs a translation. There is no overlap or ambiguity between them.
Both tool names follow a hyphenated verb-object pattern with a '-tool' suffix, which is consistent. However, 'list-all-translations-tool' actually lists translators, not translations, creating a slight terminology inconsistency.
With only two tools, the server feels minimal and borderline. While these two tools are essential for the translation domain, the count is on the low end and may feel thin for a broader utility.
The core workflow of listing translators and performing translations is fully covered. Minor gaps include no direct way to fetch translator details, but the list function likely provides sufficient context.