reminders_eventkit_search

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds 'capped' and 'read-only', but 'capped' is vague and does not clarify behavior when the limit is reached (e.g., truncation vs. error). The description adds marginal behavioral context beyond annotations.

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 that conveys the core functionality without extraneous words. It is front-loaded and efficient, though it could benefit from slight expansion for completeness.

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 presence of an output schema (not shown) and annotations, the description covers the essentials for a simple search tool. However, it lacks details on error handling, performance, or how the cap interacts with the limit parameter, which would enhance completeness.

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 0%, so the description must compensate. It only mentions 'by title', hinting at the query parameter, but fails to explain 'limit' and 'include_completed'. While parameter names are somewhat self-explanatory, the description does not adequately clarify their semantics or usage constraints.

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 searches local Reminders via EventKit by title, with a cap and read-only access. It distinguishes from sibling tools like reminders_search (possibly broader) and reminders_due (filtered by due date).

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 usage for searching local reminders by title but does not explicitly state when to use this tool over alternatives like reminders_search or reminders_due. No exclusions or alternative guidance is provided.

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