translate_all_modules

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

No annotations are provided, so the description must fully disclose behavior. It reveals the use of git diff for detection but does not mention that translation likely modifies files, whether changes are committed, or the risk of unintended modifications. The description omits key side effects and prerequisites.

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 main action and includes the method (git diff) and scope (all supported languages). Every word contributes to 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?

The description is adequate for a relatively simple tool but lacks details on output, prerequisites (e.g., existing git repo, clean working tree), and side effects of translation. With no output schema and no annotations, more context would be needed for an agent to fully anticipate tool behavior.

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 provides 100% coverage with a description for projectRoot, so the baseline is 3. The tool description adds no additional semantic details about the parameter beyond what the schema already states.

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 action: detect changes in all default strings.xml files via git diff and translate them to all supported languages. It specifies a concrete resource (all default strings.xml files) and distinguishes from the sibling translate_module by covering all modules.

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 implies usage context: for batch detection and translation across all modules. However, it does not explicitly mention alternatives like using translate_module for a single module or check_changes to only detect changes, nor does it state when not to use this tool.

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