Delete slide

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered elsewhere. The description adds no behavioral context of its own: no irreversibility warning, no permission requirements, no effect on remaining slide indices or on the deck's minimum slide count.

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?

One short, front-loaded sentence with no waste; the '(page)' parenthetical earns its place as terminology disambiguation. There is little else to structure.

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 two-parameter destructive tool with full schema coverage and clear annotations, the essentials are present. Still missing are the consequences an agent should know before deleting, such as whether deletion is reversible and any constraint on deleting the only remaining slide.

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 100%, documenting both slideId (sourced from get_presentation or list_slides) and presentationId (from the Slides URL), so baseline 3 applies. The description adds nothing beyond that.

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 slide') and clarifies the terminology with '(page)', which helps an agent map Slides API vocabulary. It does not, however, distinguish itself from the sibling delete_element, which could plausibly delete the same object.

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 versus delete_element, no prerequisites (e.g., what happens to the last slide in a deck), and no mention of how to obtain IDs beyond what the schema already says.

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