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

Annotations already establish the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds genuine value beyond them by describing the returned shape (title, slide count, last edit), disclosing that slide texts are omitted, and confirming each draft carries a viewing/editing URL. It says nothing about pagination behavior or permission requirements, which limits it to a 4.

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?

Three short sentences, front-loaded with the core action and followed by the scope caveat and the return hint. Every sentence contributes something, though the final URL sentence is somewhat detail-heavy relative to the rest.

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, the description does a reasonable job sketching the return payload and its exclusions, and annotations cover the mutation profile. The significant gap is parameter documentation: pagination and brand scoping are invisible, which an agent needs in order to call this list tool correctly.

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% across three parameters, so the description carries the full documentation burden and largely fails it. It never mentions limit, offset, or brandId — pagination semantics and the brand scoping are only faintly implied by 'the brand's'. This leaves two of three parameters entirely undocumented anywhere.

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 names a specific verb and resource ('List the brand's carousel drafts from the Carousel Studio') and enumerates the returned fields (title, slide count, last edit), so its purpose is unambiguous. It does not, however, differentiate itself from the very similar sibling list_carousel_posts or get_carousel_draft, which is the only thing keeping it out of the top band.

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?

Usage is only implied: the note that drafts exclude 'full slide texts' hints that get_carousel_draft is needed for the full content, and 'the brand's' implies a brand scope. No alternative tool is named explicitly and there are no stated preconditions or exclusions, so the agent must infer the routing itself.

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