delete_slide

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

With no annotations, the description carries the behavioral disclosure burden. It states the destructive action and the zero-based index, and mentions the return value, but it does not disclose side effects such as reindexing of remaining slides, irreversibility, or error behavior. The core behavior is clear, but context is minimal.

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 exceptionally compact, front-loads the operation, and includes only useful information: the action, the index convention, and the return value. There is no unnecessary text or duplication of schema fields.

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 low-complexity tool, the description covers the main action and return value, but it omits practical caveats such as index shifting after deletion and whether the document must remain open or be saved afterward. An agent working with multiple slides could misuse it without those hints.

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 usefully specifies that 'index' is 0-based, which the schema does not say, but it leaves 'doc_id' to be inferred from its parameter name alone.

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 names the operation ('Delete'), the target resource ('slide'), and the indexing convention ('0-based index'). This distinguishes it well from sibling tools like add_slide, read_slide, and list_slides, making the tool's purpose unambiguous.

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 gives no guidance on when to use this tool versus alternatives, no prerequisites, and no mention of important considerations like indices changing after deletion. The only usage cue is the implicit one from the verb 'Delete', which is not enough to route an agent with confidence.

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