ig_publish_carousel

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the mutation/non-destructive profile is covered. The description adds nothing beyond that: it does not say whether the post is published immediately, how a partially failing item set is handled, or what credentials are required. The 2–10 constraint it mentions is already encoded as minItems/maxItems in the schema.

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?

A single short sentence with the verb and the key constraint front-loaded and no wasted words. It is well sized, though its brevity is achieved partly by omitting necessary detail.

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 write tool with 5 parameters, 40% schema coverage, no output schema and no body of annotations to lean on, the description is far too thin. An agent is not told the credential requirements, the publish-vs-dry-run behavior, or how mixed photo/video items are accepted.

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 40% (caption and location_id carry no descriptions at all), yet the description explains none of the remaining parameters. The one detail it does give, the 2–10 item range, is already enforced by the schema's minItems/maxItems, so it contributes no new meaning.

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 gives a specific verb and resource ("Publica un carrusel") plus a cardinality constraint (2–10 photos/videos), which separates it from ig_publish_image, ig_publish_reel and ig_publish_story. It does not name those siblings explicitly, so an agent still has to infer that multi-item posts route here rather than to the single-media publishers.

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 statement of when to prefer a carousel over a single image, a reel or a story, and no mention of prerequisites such as an authenticated account or publishing-limit checks. The only guidance is implicit in the resource name.

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