app_previews_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 burden of behavioral disclosure. It implies a destructive mutation via 'DELETE' but says nothing about irreversibility, required permissions/scopes, cascading effects on the parent preview set, or what (if anything) is returned. For a delete endpoint with zero annotation coverage this is a substantial gap.

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 content is duplicated verbatim in parentheses — pure waste — and it is under-specified rather than concise. The verb is front-loaded, which is the only structural merit.

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 single-parameter destructive endpoint with no annotations and no output schema, the description should at minimum state the target resource and the destructive consequence. It provides only a route string, leaving an agent without the context needed to invoke it safely.

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, so the schema already documents it. The '{id}' path placeholder in the description adds nothing beyond the schema. 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 essentially the tool name restated as an HTTP route: 'DELETE /v1/appPreviews/{id}'. It does convey a verb (DELETE) and a resource (appPreviews), but it adds no scope, no resource description, and nothing to distinguish it from app_previews_get_instance, app_previews_update_instance, or app_previews_create_instance. That is tautology rather than clarification.

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 guidance on when to use this tool versus the sibling create/get/update app preview tools, nor any prerequisites, nor any warning about consequences. The agent is left to infer everything from the name alone.

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