screenshot_sync

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

No annotations are provided, so the description carries the full behavioral burden. It does not disclose whether syncing overwrites existing files, requires specific permissions, handles missing locales, or what the mutation effects are.

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 very short, but its brevity reflects under-specification rather than clean conciseness. It is a sentence fragment that does not front-load a clear action or resource.

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 sync tool with no annotations, 0% schema description coverage, and two required undocumented parameters, the description is far too incomplete. Even with an output schema, an agent lacks enough context to invoke 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 description coverage is 0%, and both required parameters are undocumented. The description does not name or explain marketing_dir or fastlane_screenshots_dir, nor how they map to the path fragment shown.

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 gives only a cryptic fragment: 'branded → fastlane/screenshots/<locale>/.' It implies movement of branded screenshots into fastlane's locale directory, but does not state a clear verb or fully distinguish the tool from siblings like screenshot_brand or deliver_screenshots.

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?

There is no guidance on when to use this tool, when not to use it, or which sibling tools are alternatives. The agent must infer entirely from the tool name and schema.

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