Delete a saved view

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is known. The description adds genuinely new behavior: the write is gated behind confirm, and there is no server-side dry run, so the client-side preview is the only safety net. It stops short of saying whether the delete is recoverable or affects other users' access to the view.

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?

Two tightly packed sentences with the resource, the endpoint, and the write-safety caveat front-loaded. No filler and nothing repeated unnecessarily.

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, single-parameter mutation with no output schema, the definition covers the critical unknowns: it is a write, it is confirm-gated, and there is no server-side dry run. Remaining gaps — irreversibility and scope of the deletion — are modest but would be useful before an agent commits.

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 67% and the confirm parameter is already fully documented in the schema, including the preview fallback. The description only restates that gate and notes the absence of a server-side dry run; it adds nothing about id or idempotencyKey beyond the schema.

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?

States a specific verb and resource ('Delete a saved view') and even pins the underlying endpoint DELETE /v1/saved-views/{id}, so the agent knows exactly what is being removed. It doesn't explicitly contrast with sibling savedViews_list/create, but the destructive verb makes the distinction obvious.

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 supplies an important invocation rule — nothing is executed unless confirm: true — which effectively tells the agent how to call it safely. It gives no guidance on when deletion is appropriate versus alternatives (e.g., creating a replacement view or listing views first), so usage context is only implied.

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