get_reminders

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

No annotations are provided, so the description carries the full burden. It states the tool retrieves reminders with optional filtering, but lacks critical behavioral details: it does not specify if this is a read-only operation, whether it requires authentication, how results are returned (e.g., pagination, format), or any rate limits. The description is minimal and misses key operational context.

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, efficient sentence that directly states the purpose and optional filtering. It is front-loaded with the core action and avoids unnecessary words, making it easy to parse quickly.

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 lack of annotations and output schema, the description is incomplete. It does not explain return values, error handling, or behavioral traits like safety or performance. For a tool with no structured metadata, the description should provide more context to guide the agent effectively, but it remains overly brief.

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 description coverage is 100%, with the parameter 'completed' fully documented in the schema. The description adds no additional meaning beyond what the schema provides (e.g., no examples, edge cases, or usage tips). With high schema coverage, the baseline is 3, as the description does not compensate but does not detract.

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 action ('Get all reminders') and specifies optional filtering by completion status. It distinguishes from siblings like 'get_completed_reminders' and 'get_overdue_reminders' by indicating it can retrieve all reminders or filter by completion, but does not explicitly contrast with 'search_reminders' or 'get_todays_reminders', which limits differentiation.

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 provides no guidance on when to use this tool versus alternatives like 'get_completed_reminders' (for only completed), 'get_overdue_reminders' (for overdue ones), or 'search_reminders' (for more complex queries). It mentions optional filtering but does not specify use cases or exclusions, leaving the agent to infer usage.

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