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

The description adds useful behavioral context beyond the annotations: the server controls chip layout, safezones, and export pixels, so callers should not expect to specify those details. 'Create or replace' is consistent with idempotentHint=true, and the annotations already cover read/write and destructive hints; no contradiction is evident.

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?

Two short sentences with the action front-loaded and no wasted words. The second sentence adds a meaningful behavioral boundary without repeating schema constraints.

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?

This is a complex tool with 10 parameters, nested slides/style/visual objects, and no schema descriptions. The two-sentence description leaves key semantics unexplained, including idempotency key behavior, clear_existing semantics, platform-specific constraints, and how the result relates to existing projects.

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%, so the description needed to compensate, but it only maps 'slide document' to the slides parameter. It does not explain required fields like idempotencyKey, platform, or name, nor options such as clear_existing, style, series_id, or project_id.

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 concrete action ('Create or replace a carousel project') and the input source ('a slide document'), making the core purpose clear. It doesn't name or contrast sibling tools like carousels_patch_document or carousels_clone, so it stops short of full differentiation.

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 explicit guidance about when to use this tool versus alternatives such as carousels_patch_document, carousels_preview, or carousels_migrate. The phrase 'Server owns chip layout...' hints at an automated-compilation use case, but the agent is left to infer when this is the right choice.

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