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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=false, so the safety profile is covered; the description adds nothing on top of that. It omits the behavior that actually matters for a destructive slide deletion: whether the content is recoverable, whether deck_undo_turn can reverse it, and whether subsequent slide numbers shift (important given the schema indexes slides from 1).

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 single sentence is front-loaded and contains no filler, but its brevity is under-specification rather than economy. There is room for one short clause on irreversibility or undo without bloat.

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?

This is a destructive mutation with two required parameters, no output schema, and no annotations explaining recovery. An agent cannot tell from this definition whether the deletion is permanent, whether slide numbering of remaining slides changes, or what a successful call returns, which is not sufficient for a destructive operation.

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 coverage is 100% and both parameters are documented (slide number from 1, document's id), so the schema does the work. The description contributes no additional meaning such as whether the slide index is validated against deck_list_slides output or what happens with an out-of-range index, so the baseline of 3 applies.

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?

"Deletes a slide" restates the tool name (deck_delete_slide) and annotation title ("Deck: delete slide") almost word for word. It does identify a verb and resource, but adds no scope, no differentiation from adjacent mutators like deck_edit_slide, deck_move_slide, or deck_insert_slide, and nothing about which deck is affected.

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 delete versus when to edit or move a slide, no prerequisites (does the document need to be open/locked?), and no mention of an alternative workflow. The only implicit cue is the verb itself.

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