validate_screenshot

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

Discloses key checks (dimensions, format, alpha channel) and behavior without a preset ID, but does not mention side effects, permissions, or error responses. With no annotations, more depth on return values or edge cases would be beneficial.

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 concise, front-loaded sentences with no filler. Every phrase contributes meaningful 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?

Provides behavioral details but lacks output format or success/failure indicators. Given no output schema, the description should more clearly state what the tool returns on validation pass or failure.

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 covers both parameters fully. Description adds functional context for 'preset' (reports matching preset when omitted), enhancing understanding beyond the schema alone.

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?

Describes a specific verb ('checks') and resource ('image against store requirements'), and distinguishes from siblings by detailing validation criteria (dimensions, format, alpha channel) and behavior without a preset ID.

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?

Clearly indicates when to use the tool (for validation against store requirements), but lacks explicit exclusionary guidance or comparison to sibling tools like 'list_presets' or 'compose_screenshot'.

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