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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds one genuinely non-obvious constraint — Panorama art cannot be redrawn one slide at a time — but says nothing about auth, errors, or how revisions relate to the current document. Adequate, not rich.

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 dense paragraph enumerating block types (note, pills, stat, board, steps, prompt, buttons) with their field shapes. Most of that detail is return-shape trivia, not invocation guidance, and it swamps the one sentence that matters. Poorly front-loaded relative to its size.

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?

With no output schema, describing the document/revision shape and Panorama structure does add return-value context that would otherwise be absent. However, the sole required input, projectId, is left unexplained, so an agent knows what comes back but not what to pass in.

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% and there is one parameter, projectId, which the description never mentions or explains (no format, no source, no example). The description must compensate for the schema gap and instead spends its words on Panorama block shapes that are not inputs to this call.

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 opening sentence states a specific verb and resource: read a carousel or cover's document and revision. It also implicitly distinguishes itself from studio_save by naming that sibling as the editing path. It stops short of 5 because the purpose is buried under a large amount of data-model exposition rather than leading cleanly.

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 says the retrieved fields are editable with studio_save, which implies a read-then-save workflow, but never states when to choose this tool versus studio_list, studio_job or studio_export. Usage is implied rather than instructed.

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