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

While annotations already declare readOnlyHint=true and destructiveHint=false, the description adds value by stating 'Reads only — this neither sends nor cancels an issue' (behavioral confirmation), noting the API key requirement (auth context), previewing return fields (subject, status, send time), and explaining the empty-list edge case semantics ('not an error'). No contradiction with annotations. Genuinely useful context beyond structured data.

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?

Four sentences, each earning its place: purpose, use cases + alternative, read-only clarification with auth note, and empty-list semantics. The most critical information (core purpose and ordering) is front-loaded, and every subsequent sentence adds non-redundant value. Zero wasted words.

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 simple read tool with 1 optional parameter, no output schema, and rich annotations, the description is fully complete. It covers return value semantics (subject, status, send time) despite lacking a structured output schema, explains error/empty behavior, and addresses the sibling relationship. The complexity is low, and the description fully matches that complexity budget.

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 100%, and the single parameter (limit) is already well-documented in the schema with range, default, and ordering semantics. Per the baseline rule, a 3 is appropriate since the description doesn't need to compensate for schema gaps, and it doesn't contradict the schema. The description adds no param-specific detail beyond what the schema already provides, but doesn't need to.

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 opens with a specific verb+resource+scope construction ('List newsletter issues the account has sent or scheduled, newest first'), which precisely defines what the tool does. It explicitly distinguishes itself from the sibling tool list_newsletter_subscribers by clarifying the WHO/WHAT boundary, directly addressing the sibling context.

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 description provides explicit when-to-use scenarios ('check what went out and when, or to confirm a scheduled send exists before queueing another') and names the alternative tool for a different use case ('For WHO receives them, use list_newsletter_subscribers'). This is an exemplary explicit-when-and-alternatives pattern with no ambiguity left for the agent.

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