delete_saved_view

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

Annotations already declare destructiveHint=true and readOnlyHint=false. The description adds 'permanently' and a warning, which is consistent and slightly extends the annotation. It does not disclose other behavioral aspects like the need for confirmation (though the schema covers that) or consequences of deleting a referenced view. Given the annotation coverage, the bar is lower, and the description adds some context but not rich detail.

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 sentence with a warning prefix, front-loading the destructive nature. It is efficient and wastes no words, though it is minimal. The structure is clear and appropriate for the tool's simplicity.

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 simple delete operation, the description conveys the core action and permanence. It does not explain the return value or error behavior (e.g., what happens if the id doesn't exist), but the annotations and schema cover safety and confirmation. The description is adequate but leaves some context to inference.

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 50% (only the confirm parameter has a description). The description does not mention either parameter, leaving the 'id' parameter entirely undocumented. It fails to compensate for the schema gap by explaining what id refers to. This is a significant omission for a tool with two required parameters.

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 'Permanently delete a saved view' uses a specific verb and resource, clearly stating the action. It distinguishes itself from sibling delete tools by naming the resource type, though it relies on the tool name for disambiguation. It adds the qualifier 'permanently' which is helpful.

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 provides no guidance on when to use this tool versus alternatives such as update_saved_view or get_saved_view. It only warns that the operation is destructive, which is cautionary, not a usage directive. There is no mention of when not to use it or what to use instead.

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