set_translation_mode

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

No annotations exist, so the description carries full burden. It implies a write operation but does not disclose side effects, persistence, revert options, or what 'mode' actually changes. The plan requirement is mentioned, but little else.

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 brief (5 words), which is concise, but it under-specifies the tool's purpose and inputs. It does not earn its place because it omits critical information.

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 no annotations, no output schema, and an empty input schema, the description should provide substantial context. It only states the action and a plan tier, leaving the agent without enough information to invoke the tool correctly.

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 is empty with additionalProperties allowed, yet the description does not explain what properties the tool accepts (e.g., a mode value). With 0 params, the description should compensate by specifying expected inputs; it does not.

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 states the tool 'Set translation mode' - a clear verb+resource pair. It is distinct from sibling tools like get_translation or upload_translation, though the exact meaning of 'mode' is not elaborated.

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 only usage hint is 'PRO+ plan', indicating a prerequisite but providing no guidance on when to use this tool versus alternatives like set_chat_system_prompt or update_ui_settings. No context or exclusion criteria are given.

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