Translate screenshot headings

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

Adds real context beyond the annotations: this is an asynchronous background job, and rendering/upload happen in the app rather than in the tool. It also hints at state change without contradicting destructiveHint=false. Missing only cost/rate or failure-mode details.

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?

Four short sentences, front-loaded with the action and the scope, then the prerequisite and follow-up. Slightly telegraphic phrasing ('Every slide needs a main heading first') keeps it from a 5, but nearly every sentence carries 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 fire-and-forget background mutation with no output schema, it supplies the missing pieces: it is async, the visible result appears via get_screenshots, and rendering/upload are handled elsewhere. That is enough for an agent to call it 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?

Schema coverage is 100%, so the baseline is 3. The description only reinforces the `locales` filter and says nothing about `ai` or `projectId`, so it adds little beyond the schema.

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?

States a specific verb and resource: adapting main screenshot headings into the project's other languages, optionally limited to `locales`. It is distinguishable from screenshots_write_headings via the 'Every slide needs a main heading first' prerequisite, though it never names that sibling explicitly.

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?

Gives a clear precondition (headings must already exist on every slide) and tells the agent what to do afterwards (read get_screenshots to see translated/stale/missing per locale). It lacks explicit when-not-to-use guidance or named alternatives, so it falls short of a 5.

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