Check Reminders

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

The description discloses that each returned reminder is transitioned to 'fired' status, clarifying the side effect beyond the annotations (readOnlyHint=false, destructiveHint=false). This provides valuable behavioral context that helps the agent understand the tool's mutability.

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 two sentences long, front-loading the core purpose and adding a follow-up action. No unnecessary words, every sentence adds value.

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?

Given the tool has zero parameters and an output schema (indicated in context), the description is sufficient. It fully describes the action, side effect, and next steps, leaving no gaps.

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?

With zero parameters and 100% schema coverage, the description does not need to add parameter information. The baseline score of 4 applies as the description is not required to compensate for missing schema details.

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 states the tool returns pending reminders whose deadline has passed, specifying the verb 'return' and the resource 'pending reminders'. It distinguishes itself from siblings like list_pending_reminders by indicating that reminders are transitioned to 'fired' status.

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 implies when to use (when deadline has passed) and even suggests a follow-up action (search INBOX). However, it does not explicitly state when not to use or mention alternatives like list_pending_reminders for non-destructive listing.

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