Find Empty Translations

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

No annotations are provided, so the description must carry the burden. It discloses that empty strings are present in the locale file and 'render as nothing in the UI', which is useful behavioral nuance. It doesn't specify the return format or whether the output is a list, but the read-only nature is implied by 'find' and the behavior described is sufficient for basic decisions.

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?

Three sentences: purpose, rationale, and usage guidance. Each sentence contributes new information with no redundancy or filler, making the description efficient and well-structured.

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 establishes the empty-string nuance and provides a concrete trigger scenario, which is essential for distinguishing from missing-translation tools. It doesn't mention output details or pagination, but the outputFile parameter hints at large outputs, and the description seems adequate for a read-only find tool given the schema's richness.

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 already provides detailed descriptions for all four parameters (layer, locale, outputFile, projectDir), so the description adds no additional parameter semantics. Baseline of 3 applies because schema coverage is 100%.

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 uses a specific verb ('Find') and resource ('keys whose value is an empty string'), and clarifies how this differs from missing translations, distinguishing it from sibling tools like get_missing_translations and find_undefined_keys.

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 ('after a scaffold or an interrupted translation run') and explains the context (keys that were created but never filled). It doesn't list alternatives or exclusions, but the context is clear enough for an agent to choose this tool.

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