app_screenshots_delete_instance

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, and it discloses almost nothing. The DELETE verb implies a destructive, conventionally idempotent operation, but the description never states that removal is permanent, whether it requires a specific role/scope, whether the parent screenshot set is affected, or what happens on a non-existent id.

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?

It is brief and front-loaded, but the parenthetical duplicates the exact same path string already stated, which is pure waste rather than concision. The brevity stems from under-specification, not from tight editing.

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 destructive, unannotated mutation tool with no output schema, an agent needs to know about irreversibility and permission requirements before invoking it, and none of that is present. The only thing fully covered elsewhere is the single input parameter, leaving the definition inadequate for safe invocation.

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?

With a single required parameter and 100% schema description coverage, the schema already documents 'id' as 'the id of the requested resource'. The description adds no syntax, format, or sourcing detail (e.g. where to obtain the screenshot id) beyond what the schema provides, so the baseline of 3 applies.

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 is a verbatim restatement of the tool name and title in HTTP form ('DELETE /v1/appScreenshots/{id}'), with the parenthetical merely duplicating the same string. It conveys the resource (app screenshots) and verb (delete) only as a tautology, and does nothing to distinguish this tool from the many sibling delete endpoints such as app_screenshot_sets_delete_instance or app_event_screenshots_delete_instance.

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 when-to-use, when-not-to-use, or alternative guidance is present. Nothing tells the agent whether this is the correct call versus app_screenshots_update_instance (to modify instead of remove), or when a screenshot must be deleted from its parent set first.

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