Screenshot Sync

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

Annotations already declare the safety profile (readOnly=false, idempotent=true, destructive=false, openWorld=false). The description adds genuinely useful context beyond that: 'Local only; nothing is uploaded.' It could still say more about overwrite behavior on existing locale files, so it falls short of a 5.

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 tight lines, front-loaded with the action and destination, then sequencing, then return shape. Every sentence earns its place.

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?

With an output schema present, the tool need not explain return values, and annotations cover safety and idempotency; the description adds local-only scope. Only the overwrite semantics for pre-existing locale files are undocumented.

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 both parameters are already documented in the schema; the description adds only the implied <locale> subdirectory convention. Baseline 3 is appropriate when the schema carries the parameter burden.

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 (Copy), resource (branded screenshots), and destination (fastlane/screenshots/<locale>/), so an agent knows exactly what the tool produces. It is clearly distinct from sibling screenshot_brand (which brands) and deliver_screenshots (which uploads).

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?

'Use when: after screenshot_brand, before deliver_screenshots' gives explicit pipeline ordering relative to named siblings. Nothing is left to inference about when this step runs.

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