list_reminders

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds valuable behavior: default to incomplete reminders, filtering options, and the exact return fields. This goes beyond annotations without contradicting them.

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?

Five short, information-dense sentences. Front-loaded with purpose, then filters, default behavior, use cases, and return fields. Every sentence earns its place with no redundancy or fluff.

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 list tool without an output schema, the description is thorough: it explains default behavior, optional filters, return fields, and use cases. Combined with complete schema annotations and read-only hints, the agent has everything needed 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?

Schema covers all 4 parameters with complete descriptions (100% coverage), so baseline is 3. The description adds context by mentioning 'Search by title or list name' and 'By default only shows incomplete reminders,' which maps to title/list_name/include_completed, but it doesn't provide significantly new parameter semantics beyond the schema.

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?

States a specific verb ('List') and resource ('reminders from macOS Reminders.app') with optional filters. Clearly distinguishes from sibling tools like create_reminder by focusing on read-only listing. Also specifies the returned fields, making the purpose unambiguous.

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?

Provides clear use cases: 'Use to check for existing reminders before creating new ones, or to verify a recently added reminder.' This implicitly differentiates from create_reminder and other tools. While it doesn't list exclusions, the context is sufficient for an agent to know when to apply this tool.

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