render_carousel_project

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

With no annotations, the description carries the full burden. It usefully discloses the output artifacts and their format (lossless 1080x1350 PNGs, HTML preview), but says nothing about whether outputDirectory is created or overwritten, whether rendering is long-running, or what error conditions exist.

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 front-loaded sentence with zero filler that leads with the verb and result artifacts. Nothing is wasted.

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?

The description compensates for the absent output schema by naming the produced artifacts, which is valuable. However, for a 5-parameter renderer with nested objects it omits prerequisite and failure behavior, and its '5 to 7 slide' range conflicts with the schema's 'List of 5 to 6 slides'.

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 80%, so the schema already documents nearly every parameter, including the nested author and slide objects. The description adds the render-dimension context but no per-parameter meaning beyond what the schema provides, so the baseline 3 applies.

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 (Renders), resource (carousel project), and concrete outputs (1080x1350 lossless PNGs plus an interactive HTML preview). This clearly distinguishes it from the read-only siblings get_design_rules, list_creative_archetypes, and list_design_primitives.

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?

No when-to-use guidance, no prerequisites, and no mention of the sibling tools that supply the design rules or archetypes this renderer presumably consumes. The agent must infer that this is the terminal/execution step of the workflow.

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