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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds a small amount of scope context (which artifacts are read) but discloses nothing beyond that, such as auth requirements or side effects — acceptable given the annotation coverage.

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 that states both the action and the two resources read with no filler. It is slightly under-specified, but every word earns its place.

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 tool is simple (2 params, 1 required), annotations cover safety, and an output schema exists, so the description need not explain return values. The main gaps are parameter semantics and the meaning of the nullable workspaceId, which leaves the description adequate but not complete.

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 only 50%: projectId has a tautological 'UUID string' description and workspaceId has none. The description does not compensate by explaining what projectId identifies, what workspaceId null means, or how the parameters relate to the slot document/template catalog.

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 ('Read') and identifies distinct resources ('carousel slot document and the named template catalog'), which separates it from sibling carousel tools like carousels_patch_document, carousels_compile, and carousels_preview. It does not explicitly contrast itself with those siblings, but naming the exact artifacts read is enough to disambiguate the core intent.

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?

The description gives no guidance on when to use this tool versus alternatives such as carousels_preview, carousels_kit, or characters_get. Usage is only weakly implied by the verb, and no prerequisites, exclusions, or sibling routing are mentioned.

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