delete-view

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states 'Delete' but does not indicate that the operation is permanent, whether it has dependencies, cascading effects, or requires specific permissions. The description adds minimal value beyond the tool's 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?

The description is a single, concise sentence with no wasted words. It is appropriately short for a simple delete operation, though it could benefit from additional context without becoming verbose.

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 is simple (one parameter, no output schema), but the description does not mention consequences, return behavior, or when deletion is allowed. It lacks the contextual richness needed for an agent to use it safely, but it is minimally adequate for a straightforward delete.

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?

The schema provides only 'view_id' as a required string with no description (0% coverage). The tool description does not explain the parameter. However, the parameter name is fairly self-explanatory given the tool's purpose, but the description itself adds no semantics or format details.

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 'Delete a UI view' uses a specific verb ('Delete') and names the resource ('UI view'), which clearly distinguishes it from siblings like create-view, update-view, and get-view. It unambiguously states the core function.

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, prerequisites, or alternatives. It does not mention any exclusions or compare with other delete tools or view-related tools. The usage is only implied by the basic action.

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