search_reminders

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

No annotations are present, so the description must carry the full burden. It states the tool returns structured JSON with matches or errors, implying a read-only operation, but does not explicitly clarify non-destructive behavior, permissions, or other traits.

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 brief and structured with Args/Returns sections. It is front-loaded with the main purpose and provides parameter details without unnecessary verbosity.

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 a brief output schema (only mentioned in text), the description provides basic return info but omits potential limitations, error handling, or performance characteristics. For a search tool among many siblings, more context would be helpful.

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 0% schema description coverage, the description adds meaningful context: 'Text to match in reminder names' for query, 'Optional Reminders list name' for list_name, and 'Include completed reminders' for include_completed. This compensates well for the schema's lack of descriptions.

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 it searches reminders by name. The verb 'search' and resource 'reminders' are explicit, and parameters confirm it filters by name. It distinguishes from siblings like 'list_reminders' and 'show_reminder', but could be more precise about the search scope.

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?

No guidance is provided on when to use this tool versus alternatives like 'list_reminders' or 'show_reminder'. The description does not specify preferred scenarios or exclusions.

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