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

Annotations already establish the safe/idempotent read profile, so the bar is lower. The description adds genuinely useful context beyond them: it returns a URL for viewing/editing in the Dalea Carousel Studio and explicitly states no image files are returned, which heads off a likely agent expectation.

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 tight sentences that front-load the core action and payload, then add the return-format caveat. Nothing is wasteful, though the parenthetical payload list is slightly dense.

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 meaningfully covers the return shape (slides, funnelStage, URL, no images). The main remaining gap is parameter meaning, which drags completeness down for what is otherwise a well-covered read tool.

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 carries the full burden for draftId (required) and brandId (optional). It says nothing about what either parameter means or how brandId scopes the lookup, leaving both undocumented in both schema and description.

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 and resource ('Get one carousel draft') and enumerates the payload (slides, funnelStage values). The singular 'one' implicitly contrasts with the sibling list_carousel_drafts, but the description never names that sibling, so the differentiation is left to inference.

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: retrieving a single draft by draftId. No explicit when-to-use statement, no prerequisites, and no mention of when to prefer list_carousel_drafts versus this tool. Adequate but with clear gaps.

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