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

Annotations already declare destructiveHint=true and idempotentHint=false; the description goes beyond them by disclosing that deleting a paid-background slide discards spend, that expectedVersion is mandatory, and that a stale version fails before any work is done. It also notes the operation is free. It stops short of describing the return payload or whether other slides shift/re-index after deletion, which is relevant for a destructive non-idempotent op.

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?

Five sentences, all load-bearing: trigger first, scope second, then the confirmation gate, then the concurrency contract, then the cost note. No repetition of the title or schema fields verbatim.

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, non-idempotent, version-guarded mutation with no output schema, the description covers the confirmation gate, the version requirement, the conflict-recovery loop, and the billing side effect. Nothing essential to a correct invocation is missing.

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 only 43% across 7 params, so the description must compensate; it covers the two risky ones (confirmDropPaid as a confirmation gate, expectedVersion as the concurrency token with its DECK_CONFLICT failure mode). The remaining params (locale, accountHandle, and unlabeled deckId/slideId) get no semantic help beyond their obvious names, leaving deck scoping and the Canvas-related projectId lightly explained.

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 — 'remove a slide', 'Delete one slide from the deck' — and scopes it to exactly one slide. This clearly separates it from sibling mutations like antix_add_slide, antix_reorder_slides, and antix_edit_deck_slides.

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?

Gives an explicit trigger ('when the user asks to remove a slide'), a prerequisite gate for paid backgrounds requiring user confirmation before proceeding, and a recovery path on DECK_CONFLICT. An agent knows when to call it, when to pause for approval, and what to do on failure.

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