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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description goes beyond them by disclosing the filtering behavior (pending only, so completed reminders are excluded), the sort order (soonest first), and the shape of each returned item (task title and due date). No auth or rate-limit caveats, but the added behavioral context is substantive.

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?

One sentence, front-loaded with the primary action and resource, then progressively narrowing with ordering, optional filter, and return fields. No filler or redundancy.

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 no output schema, the description usefully summarizes the return payload (each task's title and due date), and the whole tool is a simple two-param read. The main gap is that it doesn't say whether results are capped, paginated, or how the limit interacts with the ordering, but that is minor for a read-only list.

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 50%: limit is documented in the schema ('Default 50, max 200') while boardId has no schema description. The description compensates for boardId only by implication ('optionally on one board'), with no format, default, or behavior for invalid/multi-board values. Baseline 3 is appropriate for this mixed coverage.

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?

Specific verb (Lists) plus resource (user's pending reminders), with added scope detail: pending only, soonest first, optionally scoped to one board. It is clearly distinct from add_reminder/remove_reminder and from task-list siblings, though it does not name the nearest alternative (e.g. list_my_tasks) to sharpen the boundary.

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 phrase 'optionally on one board' implies when to use boardId, which is useful implied guidance. However, there is no explicit when-to-use framing, no statement of what it excludes relative to list_my_tasks or list_notifications, and no guidance on when to raise the limit.

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