Delete Screenshot or Set

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

Explicitly states that deleting a set cascades to all screenshots in it, adding behavioral context beyond annotations. Annotations already mark destructiveHint=true, but description clarifies the cascading effect.

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?

Single sentence, front-loaded with verb, no wasted words. Efficiently conveys the core action.

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?

Adequately explains behavior for both resource types given low complexity (2 params, no output schema). Lacks potential error conditions or authorization requirements, but acceptable for a simple tool.

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 0%, so description must compensate. It explains the distinction between 'screenshot' and 'set' resource types but does not clarify the 'id' parameter or provide any format/example. Partial compensation.

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 clearly specifies the verb (delete) and the resource (screenshot or set), and distinguishes between deleting a single screenshot versus a set that deletes all contained screenshots. This is distinct from sibling tools.

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?

No guidance on when to use this tool versus alternatives. There are no other delete tools in siblings, but description does not mention prerequisites, conditions, or exclusions.

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