app_preview_sets_delete_instance

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

With no annotations provided, the description carries the full burden, and it does not disclose any behavioral traits. 'DELETE' implies an irreversible mutation, but there is no statement about required permissions, cascading effects on child app previews, or whether the deletion is reversible or recoverable.

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 the parentheses, which is pure redundancy rather than conciseness. Front-loading is fine, but a third of the text earns nothing.

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 mutation with no annotations, no output schema, and no behavioral disclosure, the description is inadequate. An agent cannot tell whether the deletion is safe, what it requires, or what side effects it has, so it is not complete enough to call the tool confidently.

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% and the single parameter ('id') is fully documented in the schema, so the baseline is 3. The description adds no syntax, format, or meaning beyond what the schema already provides.

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 a restatement of the tool name: 'DELETE /v1/appPreviewSets/{id}', and the parenthetical duplicates the same path verbatim. It does convey the verb (delete) and resource (app preview set), but it adds nothing an agent couldn't infer from the name and offers no differentiation from the many sibling delete tools.

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 whatsoever on when to use this tool, prerequisites, or alternatives (e.g., app_previews_delete_instance vs. app_preview_sets_delete_instance). The agent is left to infer everything from the name.

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