[Destructive/Release] Delete a screenshot

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

With no annotations, the description carries the full burden of disclosing behavior. It explicitly warns 'DESTRUCTIVE' and states 'Permanently removes', making the irreversible nature clear. It also scopes the action to a single screenshot. It does not mention auth needs or rate limits, but for a destructive operation, the key safety trait is 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?

The description is two sentences, front-loaded with the 'DESTRUCTIVE' warning, and every word serves a purpose. It is concise and well-structured, with no filler.

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?

The tool has one parameter, no output schema, and no annotations, but the description covers the essential aspects: what it does, the destructive consequence, and how to get the required ID. It lacks some operational details like error handling or return values, but given the low complexity, the description is sufficiently complete.

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?

The schema already describes screenshotId as 'App Store Connect appScreenshot id to delete.' The description adds meaning by specifying where to obtain this id (from asc_screenshot_sets_list results), which helps the agent understand the provenance of the parameter value. This goes beyond the schema's basic definition.

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 tool's function: 'Permanently removes a single screenshot from App Store Connect.' The verb 'removes' and resource 'screenshot' are specific, and the action is distinguished from sibling tools like asc_screenshot_upload (upload) and asc_screenshot_sets_list (list).

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?

It provides a clear prerequisite: 'Get the screenshot id from asc_screenshot_sets_list results (each set's screenshots) before calling this.' This tells the agent exactly how to obtain a valid input and implies the tool should be used only when deleting a screenshot. However, it lacks explicit 'when not to use' or alternative tool guidance beyond the prerequisite, so a perfect score is not warranted.

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