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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds useful context by explaining that only pending reminders are returned and that each reminder includes its associated item, which matters because there is no output schema. It does not mention ordering, pagination, or limits, but those are minor for a simple read-only listing.

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 that states the action, scope, and output content with no filler. Every part earns its place.

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 zero-parameter, read-only listing tool, the description gives enough information for an agent to call it successfully: it names the resource, the pending filter, and the associated item returned. Since there is no output schema, mentioning the attached item is valuable; lack of ordering or pagination detail is a minor gap.

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 tool has zero parameters and the schema already fully communicates that. With no parameters to document, there is nothing missing from the description; the baseline of 4 applies.

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 uses a specific verb ('list'), a specific resource ('the user's pending reminders'), and an explicit scoping condition ('not-yet-sent'). It also clarifies the returned content ('with the item they're on'), which distinguishes this from sibling tools like cancel_reminder, create_reminder, and list_categories.

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 makes the usage context clear by restricting results to pending, not-yet-sent reminders, which implicitly tells an agent when this tool is appropriate. It does not explicitly name alternatives or when-not-to-use scenarios, but the scoping language is strong enough for an agent to route correctly.

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