invariance_saved_view_delete

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

The description says 'Delete', which aligns with destructiveHint=true, but it adds no behavioral detail beyond the annotations: it does not state that the deletion is permanent, irreversible, or whether any other objects are affected. The annotation already carries destructive meaning, and the description adds only the resource 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 one short, direct sentence: 'Delete a saved view by ID.' It is front-loaded, no filler, and the key action is the first word. For a one-parameter delete tool, this is concise.

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 simple schema and annotations, the description is enough to confirm the operation, but it lacks context about consequences expected results, or where the ID can be obtained. The presence of destructiveHint eases this, but 'by ID' alone does not fully contextualize the deletion need.

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 0%, so the description must compensate. It only repeats 'by ID', matching the schema property 'id' without explaining what the ID refers to, where to find it before deleting, or any expected format. This is minimal rescue and doesn't practically add 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?

Description uses the specific verb 'Delete' and clearly identifies the resource type ('a saved view') and the operation mode ('by ID'). Among many invocation_saved_view_* siblings, this immediately stands apart as the destructive deletion operation versus create/get/update/run.

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 invoke vs an alternative, no prerequisites beyond the ID, and no statement about when not to use it. The sibling list includes saved_view_create/update/get, so an agent is left to infer that delete is only for removing, not for changing or reading.

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