Delete a slide or element

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

Annotations already mark destructiveHint=true, and the description adds valuable consequences: deleting a slide removes its elements and speaker notes, deleting a group removes children, and there is no API-level undo. This goes well beyond the annotations and prepares the agent for irreversible side effects.

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?

Three sentences, each earning its place: the core action, the destructive side effects, and the key limitation. The main behavior is front-loaded and the caveats are 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?

For a destructive single-object deletion tool, the description covers the operation, side-effect cascading, irreversibility, and an important boundary (cannot delete the whole presentation). Combined with full schema coverage and destructiveHint, this is complete enough for an agent to call safely and interpret behavior.

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%, and the input schema already documents both presentation_id and object_id, including where each comes from. The description does not add much parameter-specific meaning beyond saying deletion is by object id, so 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?

States a specific verb and resource: deletes a slide or page element by object id. It also explicitly scopes what it cannot do (delete the whole presentation), which helps distinguish this tool from Drive-level operations.

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?

Clearly frames when the tool is appropriate: deleting a slide or element by object id. It also gives an explicit exclusion for whole-presentation deletion. However, it does not directly discuss when to prefer batch_update for multiple deletions or other combined operations.

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