Discover i18n Setup

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

No annotations exist, so the description carries full burden. It discloses that the tool returns config and directory listings and warms the cache. It adds behavioral context (cache side effect) beyond the schema, though doesn't cover authorization or errors. For a read-only discovery tool, this is transparent.

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, zero wasted words. First sentence details return contents, second provides usage guidance. Front-loaded with purpose, highly efficient.

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 1 optional parameter and no output schema, the description covers key aspects: what it returns (config elements, directory listings) and critical usage order. It lacks mention of output format or errors, but is sufficient given sibling tools' domain.

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 has 1 parameter with 100% description coverage. The description does not add extra detail beyond the schema (projectDir is optional, defaults to cwd). Baseline 3 is appropriate as schema already documents the parameter adequately.

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 discovers the complete i18n setup, listing specific return contents (config, directory listings). The verb 'discover' and resource 'i18n setup' are specific, and it distinguishes from sibling tools focused on individual translation operations.

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 explicitly says 'Call this first — it warms the config cache that all other tools depend on.' This provides clear context on when to use it, establishing a dependency order. No exclusions or alternatives are mentioned, but the guidance is strong.

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