charlotte_screenshot_delete

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

The description notes that the file is 'removed from disk', indicating permanent deletion. However, with no annotations, more detail would be helpful (e.g., irreversibility, authorization needs). The behavioral trait is adequately but minimally disclosed.

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 sentences, 14 words total. Every word is essential. No redundancy or unnecessary detail.

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 simple deletion tool with one parameter and no output schema, the description covers the core purpose and effect. Lacks error handling or side effect details, but is adequate given simplicity.

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% with a clear description of the 'id' parameter. The tool description adds 'by its ID' but does not significantly augment the schema's description. Baseline score is appropriate.

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 states the verb 'delete', the resource 'saved screenshot artifact', and the effect 'removes the file from disk'. It distinguishes itself from sibling tools like charlotte_screenshot (capture) and charlotte_screenshot_get (retrieve).

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 vs. alternatives (e.g., charlotte_screenshots to list, or charlotte_screenshot_get to retrieve). No mention of prerequisites or exclusions.

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