delete_slide

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

No annotations are provided, so the description must disclose behavioral traits. It states the action is permanent ('permanently'), which is a key behavioral trait. However, it does not mention auth requirements, reversibility, side effects, or error conditions. Without annotations, the description carries the full burden, and it falls short.

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 two sentences, concise and front-loaded. No unnecessary words but could be slightly more informative.

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 tool is a simple delete operation with no output schema, the description partially covers the necessary context. It lacks details on return value, error handling, or what happens if the slide doesn't exist, but is somewhat adequate for a straightforward delete.

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?

The input schema has 100% description coverage, describing both parameters. The description adds no extra meaning beyond what the schema provides; it does not elaborate on presentation_id or slide_id. Thus, the value added is minimal.

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 clearly states it removes a slide permanently from a presentation, specifying both the verb (delete/remove) and resource (slide). However, it does not differentiate from the sibling tool 'delete_presentation', which deletes a whole presentation instead of a slide.

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 explicitly says 'Use this only when you know the exact slide identifier to delete', providing clear guidance on when to use the tool. It implies that you should not use it without knowledge of the slide identifier, but does not mention when not to use it or alternatives.

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