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

Adds substantial context beyond the thin annotations: FREE, moderation of caption + hashtags + image bytes with nothing posting on refusal, and the exportSource resolution rule (browser-finalized export wins; server_rendered is a vector approximation that must be disclosed). Annotations only declare idempotentHint=false and destructiveHint=false, so this added detail is valuable. It never explains that idempotencyKey is the retry-safety mechanism despite idempotentHint=false.

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?

Front-loaded with the core action and the publish target, then layers the details that matter (export resolution, URL reuse, moderation, no Instagram). Dense but nearly every clause carries operational information; the Instagram paragraph is somewhat long relative to its single fact.

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?

No output schema exists, yet the description explains the key response fields (exportSource values, slideUrls[] ordering and permanence, publish.instagram.available=false) and failure behavior, which is exactly what an agent needs. The gap is input-side: with five parameters and zero schema descriptions, an agent gets no guidance on caption/hashtags/accountHandle/idempotencyKey usage.

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 0% across 5 parameters, and the description mentions no parameter by name — caption limits, hashtag count/moderated status, accountHandle, and especially idempotencyKey semantics are entirely undocumented. The only implicit parameter mapping is 'a finished carousel deck' → deckId, which the required field already conveys.

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+resource+destination: 'Publish a finished carousel deck to the AIGORA feed — the only live publish target.' It explicitly distinguishes itself from antix_create_post (moderation pipeline reference) and antix_export_deck (scheduling handoff), and rules out Instagram in bold.

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 clear when-to-use context ('the only live publish target'), tells the agent what to do with the output (hand slideUrls[] to a scheduler, never re-derive), and names a hard exclusion (no Instagram autopublish). It does not state preconditions such as deck readiness (e.g., antix_check_deck_readiness) or when to prefer antix_create_post instead.

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