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

Annotations only say non-idempotent and non-destructive; the description adds the copy-then-insert semantics, place-after-source behavior, the required expectedVersion with the DECK_CONFLICT read-and-retry protocol, and that the call is free. These are exactly the operational facts an agent needs before invoking a mutating, version-gated tool.

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?

Four tight sentences: trigger first, then mechanics, then the follow-up dependency, then the conflict/cost note. No filler or restatement of the tool name.

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 6-parameter mutation tool with no output schema, the description covers the essential flow and failure mode. It would be stronger if it stated whether a new slide ID is returned so the agent can chain antix_set_slide_copy, and what locale/accountHandle/projectId affect.

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 only 33%, so the description must compensate. It does add real meaning for afterSlideId (defaults to last slide) and expectedVersion (stale value fails with DECK_CONFLICT), but deckId, locale, accountHandle, and projectId are left to the schema with no clarification.

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 operation — copying an existing slide and inserting the duplicate immediately after the original — with the placement parameter named and the default behavior spelled out. This clearly separates it from siblings such as antix_delete_slide, antix_reorder_slides, and antix_create_deck.

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?

"Use this when the user asks to add or duplicate a slide" gives an explicit trigger, and the description routes the agent onward to antix_set_slide_copy for content. It stops short of naming when NOT to use it (e.g. versus antix_edit_deck_slides or antix_create_deck), so no explicit exclusions.

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