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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful pipeline context by naming which fields are editable downstream via studio_save, but says nothing about auth requirements, failure modes, or response shape beyond 'document and revision'.

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 compact sentences with no filler, and the read scope is front-loaded ahead of the studio_save editing note. Slightly compressed jargon ('document and revision') costs a bit of clarity but there is no waste.

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 single-parameter read tool with no output schema and read-only annotations, the description covers the core read scope and the edit pathway adequately. It is thin on how to obtain a projectId and on the shape of the returned document, which keeps it from a 5.

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 the description never mentions projectId or where a valid project id comes from (e.g., studio_list or studio_templates). With a required, undocumented identifier, the description fails to compensate for the schema gap. Only the loose association between 'carousel or cover' and a project partially helps.

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 resource (a carousel or cover's document and revision), which an agent can distinguish from the sibling studio_save and from generic post readers like get_post. It does not explicitly contrast itself with other studio_* tools beyond the editing counterpart, so it falls just short of a 5.

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 mention that text, slide order, style, format and image references '(are) editable with studio_save' implicitly routes the agent to the write path and implies this tool is the read counterpart. However, there is no explicit when-to-use statement, no prerequisites, and no guidance against using it for non-carousel/cover posts.

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