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

Beyond the destructiveHint annotation, the description explains that replacing a paid picture requires confirmDropPaid:true and user confirmation, that foreign hosts are refused, that luma recolors the copy, and that stale expectedVersion causes DECK_CONFLICT. These are meaningful behavioral constraints and failure modes not covered by the annotations alone.

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 front-loaded with the main action and host restriction, then proceeds through the key alternative, paid-replacement warning, concurrency rule, and cost note. Each sentence carries useful routing or safety information without filler.

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 mutation with no output schema, the description covers the core usage, alternative, safety confirmation, host restriction, and conflict handling well. It is not fully complete because several optional parameters and the success return behavior are left for the schema or inference.

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 44%, and the description adds critical meaning for url, luma, confirmDropPaid, and expectedVersion. However, several parameters such as deckId, slideId, locale, accountHandle, and projectId remain undocumented in the prose, so it only partially compensates for the low schema coverage.

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 uses a specific verb and resource: put an already-stored AIGE image on one slide as its picture. It immediately distinguishes the scope by restricting the URL to AIGE storage hosts and explicitly names the different sibling tool for files from the conversation.

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?

It states exactly when to use this tool versus antix_attach_deck_image: stored AIGE https link versus a conversation file. It also gives concrete operational guidance for paid-picture replacement and for handling DECK_CONFLICT.

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