Show reminders

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

Since no annotations are provided, the description carries the full burden of behavioral disclosure. 'List' implies a read-only operation, and 'pending desktop reminders' specifies scope, but it does not explicitly state that the tool has no side effects or that it doesn't modify anything. For a simple read tool, this is sufficient but could be more explicit about non-mutation.

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 sentence with no wasted words. The action is front-loaded and the output format is mentioned at the end. Perfectly concise.

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 tool with no output schema, the description provides the necessary information: what it does (list), what it lists (pending desktop reminders), and the output format (structured JSON). No additional context is required for an agent to invoke it correctly.

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, so the schema coverage is trivially 100%. Per the baseline for zero-parameter tools, a score of 4 is appropriate; there is nothing to document.

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') and resource ('pending desktop reminders'), and specifies the output format ('structured JSON'). It clearly distinguishes from sibling tools like reminder_set and reminder_clear, which mutate state. A single sentence conveys exactly what the tool does.

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 does not explicitly state when to use this tool versus alternatives, but the context is clear: it's a read-only query for reminders. It doesn't mention any prerequisites or exclusions, but for a zero-parameter tool with a single obvious purpose, the implied usage is sufficient. A 4 reflects clear context without explicit alternatives.

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