delete_view

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

No annotations are provided, so the description carries the full burden. It indicates a destructive action ('delete') but does not disclose permanence, authorization requirements, what constitutes a 'valid preview', or consequences of invalid input. Minimal behavioral context beyond the obvious.

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 a single concise sentence with no redundancy. It is front-loaded with the action and includes the essential prerequisite, making it efficient and clear.

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 low complexity (1 param, no output schema), but as a mutation tool with no annotations, the description lacks workflow guidance. It does not mention that this is the execution step after preview_delete_view, nor address side effects or return values. The dependency on a 'valid preview' is unexplained, making it incomplete 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 coverage is 0%, so the description must add meaning. It clarifies that previewId should be a valid preview identifier from a preview operation, adding context beyond the schema's type/minLength. However, it does not explain how to obtain or validate that preview.

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 action (delete) and the target (a view), and specifies a prerequisite ('valid preview'). This distinguishes it from sibling tools like preview_delete_view (which only previews) and apply_view_update.

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?

The phrase 'using a valid preview' implies that a preview must have been created first, likely via preview_delete_view, but it does not explicitly state when to use this tool vs alternatives or when not to use it. No direct exclusions or alternative references are provided.

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