delete_view

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

Annotations already indicate destructiveHint=true, and the description adds the key behavioral constraint of not allowing deletion of the last remaining view. This goes beyond the annotation by specifying a boundary condition, which is valuable for the agent.

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 two sentences: one for the primary action and one for a critical constraint. Every word is necessary; no fluff or redundancy. Properly front-loaded with the verb and resource.

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?

Given the annotations (destructive, no idempotency) and lack of output schema, the description provides adequate information: what it does, the required parameters, and a key limitation. It is complete for a simple deletion tool, though it could theoretically mention side effects like cascading deletions, but such detail is not standard.

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 input schema has 100% description coverage, so the description does not need to add much parameter-level detail. The tool description does not provide additional meaning beyond what the schema already offers for appId, viewId, and debug. Baseline 3 is appropriate.

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 resource (view from a table). It also adds a specific constraint ('Cannot delete the last remaining view'), which distinguishes it from sibling tools like delete_field or delete_table.

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 description gives context about a limitation (cannot delete last view), but does not explicitly state when to use this tool versus alternatives like delete_view_section or when not to use it. The constraint implies guidance, but lacks explicit when/when-not statements.

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