delete_slide

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

The description only says 'Remove' but does not disclose destructive side effects, error conditions, or any behavioral requirements. With no annotations, the description fails to inform the agent about the tool's implications.

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 very concise, consisting of a single sentence. However, it sacrifices necessary details for brevity. It is not optimally structured, lacking any front-loading of critical information.

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 has one parameter with no schema description, no annotations, and an output schema, the description is severely incomplete. It does not explain the return value, parameter meaning, or context of the 'bound presentation'. The description leaves many gaps for an AI agent.

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 one parameter (slide_index) with no description, and the tool description does not elaborate on how the parameter should be used or its valid range. Schema description coverage is 0%, and the description adds no value.

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 the verb 'Remove' and the resource 'a slide from the bound presentation', making the tool's purpose unambiguous. It's distinct from sibling tools like add_slide or reorder_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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of constraints, prerequisites, or when not to use it.

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