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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world). The description adds a real behavioral trait beyond them: a hard 50-draft ceiling that makes it unusable as a counting source. It does not add pagination or ordering-detail context, so it falls short of the top band.

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 short sentences with zero filler; the purpose leads and the caveat follows immediately. Every sentence carries information an agent needs.

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 an output schema present, return values need no explanation, and the description supplies purpose, exclusion, and the item cap. It is close to complete for a one-optional-param list tool, missing only ordering details that the output schema likely covers.

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?

The single parameter is fully documented in the schema (coverage 100%, default 10 / max 50), which sets the baseline at 3. The description restates the 50 cap but adds no syntax, range behavior, or interaction detail for 'limit' beyond the schema text.

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 (List) plus resource and scope (most recently created inbox drafts), which separates it from search_drafts and list_recent_notes without opening either schema. The scoping adjective 'recently created' is meaningful and front-loaded.

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?

Explicitly gives a when-not condition ('Not for counting ... cannot tell how many the user has') with the reason, which cleanly routes the agent away from count_drafts. It stops short of naming count_drafts as the alternative tool or addressing search_drafts for filtered retrieval.

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