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

Annotations already declare the full safety profile (readOnly=true, idempotent=true, destructive=false, openWorld=false). The description adds one genuinely new trait — results are ordered newest-creation-first — but says nothing about default page size, pagination limits, or how the inbox scope behaves. With annotations carrying the safety burden, the added ordering detail earns a middling score.

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 clean, front-loaded sentence with no filler or repetition. It is efficient, though arguably under-sized for a four-parameter list tool whose scope and paging behavior could use a clause or two.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. However, the description omits usage routing and leaves limit/inbox_id semantics unexplained, leaving real gaps for a tool with this many siblings.

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 coverage is only 50%: limit and inbox_id have no schema descriptions, and the tool description fills neither gap, merely implying an inbox filter via 'in an inbox'. With half the parameters undocumented in both places, the description fails to compensate.

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 ('Find'), resource ('saved drafts'), scope ('in an inbox'), and ordering ('newest creation first'), so an agent can tell it apart from single-item siblings like get_draft. It doesn't explicitly name competing list siblings (list_messages, list_sent), but the resource noun does the differentiation implicitly.

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?

No explicit when-to-use versus alternatives appears in the description; it never says to prefer this over get_draft or when list_drafts is the right call. The state parameter's schema text ('use all to reconcile...') offers guidance, but that lives in the schema, not the description.

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