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

Annotations already establish that this is a safe, read-only, idempotent operation. The description adds useful behavioral context beyond those annotations by explaining the return ordering and noting that each draft includes a mailto link addressed and filled in.

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?

The description is a single, front-loaded sentence with no wasted text. It efficiently communicates the resource, result ordering, and the mailto behavior.

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-only listing tool with one optional filter, the description covers the main return shape and ordering without needing to explain safety, since annotations handle that. It could be slightly more complete by mentioning the status filter or the discarded state, but the core behavior is adequately described.

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 optional status parameter is fully documented in the schema as an enum with 'Only this status.' The description itself does not explain the status filter, so it adds no semantic value beyond the schema, which merits the baseline 3.

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 clearly identifies the resource as payment reminders and describes what the listing contains: drafts first, then sent reminders with timing and mailto links. It does not explicitly state a verb like 'list' or name sibling tools such as solo_get_reminder or solo_draft_reminder, so it stops short of full sibling differentiation.

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 gives no explicit guidance on when to use this tool versus alternatives such as solo_get_reminder, solo_draft_reminder, solo_outstanding, or solo_statement. Usage is only implied by the noun phrase 'Payment reminders' and the described ordering.

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