subscription_app_store_review_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 nothing: not that the operation is destructive/irreversible, not whether it requires authentication or specific roles, not whether deleting the screenshot affects the parent subscription review. The verb 'DELETE' is the only signal, and it is already in the tool name.

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 short, but the entire content is duplicated in parentheses ('(DELETE /v1/subscriptionAppStoreReviewScreenshots/{id})'), so half the text is pure redundancy with zero informational value.

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 endpoint with no annotations and no output schema, an agent needs at minimum a warning about irreversibility and permission requirements. The description supplies none, leaving the definition barely adequate for correct 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?

Schema description coverage is 100% for the single 'id' parameter ('the id of the requested resource'), so the schema already documents the input. The description adds no format, source, or constraint detail beyond it; baseline 3 applies when the schema does the heavy lifting.

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 as an HTTP route: 'DELETE /v1/subscriptionAppStoreReviewScreenshots/{id}'. It identifies the verb and resource but adds no scope, target semantics, or differentiation from siblings such as subscription_app_store_review_screenshots_get_instance or update_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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. An agent learns nothing about when deletion is appropriate versus updating or replacing the screenshot.

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