apple_reminders_lists

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

No annotations are provided, so the description must disclose behavioral traits. It states it returns a JSON array of {name, count}, which is read-only behavior, but does not explicitly label it as read-only or mention any potential side effects. For a list operation, this is adequate but not fully transparent.

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 two clear sentences, no wasted words. It is front-loaded with the core purpose and includes essential return type information. Every sentence earns its place.

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 zero parameters, no output schema, and no annotations, the description covers the essential behavior: listing all reminder lists with counts. Minor gaps exist (e.g., no mention of ordering, empty list behavior, or user scope), but it is largely complete for a simple list tool.

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?

There are zero parameters, so the input schema is fully covered. Per rubric, baseline is 4. The description adds value by specifying the return format, which aids the agent in understanding output.

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 'List all reminder lists with reminder counts' and specifies the return format. The verb 'List' and resource 'reminder lists' are specific, and it distinguishes from sibling tools like apple_reminders_list (which likely lists reminders within a list).

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 apple_reminders_list, apple_reminders_search, or apple_reminders_due. It does not mention context, prerequisites, or exclusion scenarios.

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