apple_reminders_search

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false. The description adds useful search-scope context by specifying that only reminder titles are searched within selected lists, but it does not describe return behavior, matching semantics, or completion handling beyond what the schema defaults imply.

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 front-loaded sentence with no bloat, which is appropriately concise. The 'Read-only:' prefix is somewhat redundant with the readOnlyHint annotation, slightly reducing its structural value.

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 4-parameter search tool with no output schema and no schema descriptions, the definition is too thin. It does not explain return values, pagination/limit behavior, completion filtering, or query matching, leaving the agent with insufficient context to invoke it confidently.

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 for all four parameters. It only hints at 'selected lists' and 'titles' for the lists and query parameters, leaving limit and includeCompleted completely unexplained, along with query matching syntax.

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 states a specific verb ('search') and narrowed resource ('reminder titles') with scope ('within selected lists'), which distinguishes it from broader list/get reminder tools. However, it does not explicitly name or contrast with sibling tools such as apple_reminders_list, so it falls just short of a 5.

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 gives only implied usage: search reminder titles in selected lists. It provides no explicit guidance on when to use this instead of apple_reminders_list or apple_reminders_get, and no exclusions or prerequisites are stated.

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