create_carousel

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that slide ids are auto-generated and must not be supplied, but says nothing about permissions, whether creation is reversible, or what the call returns. Partial disclosure only.

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?

Three compact sentences, front-loaded with the core action, then the required slide contract, then the structural convention. No filler and every sentence carries information an agent needs.

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 creation tool with no output schema and no annotations, the description omits what is returned (e.g. the new carousel id) and any cross-tool linking guidance, even though create_variant/format=carousel and variant_id are relevant. The slide contract is covered, but the post-call picture is not.

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 100%, so the baseline is 3, but the description adds value beyond the schema by enumerating the required per-slide fields (templateId, category, label, content) and warning that ids are auto-generated. It does not clarify caption or variant_id semantics, but the added slide-shape guidance is meaningful.

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 states a specific verb (Create) and resource (carousel) and immediately scopes it with 'with the given slides,' which cleanly separates it from get_carousel, update_carousel, and list_carousels. An agent knows exactly what the tool produces without opening the schema.

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 offers structural guidance ('1 cover slide + several body slides + 1 cta slide') that implies how a carousel is typically composed, but never says when to choose this over siblings like create_content or create_variant. No alternatives or preconditions are named, leaving usage to inference.

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