apple_reminders_list_lists

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

Annotations already disclose readOnlyHint, idempotentHint, and destructiveHint, so the description's 'Read-only' prefix is redundant. It adds the 'local' scope and a practical use case, but does not reveal further behavioral traits such as return format specifics or potential limitations. The description does not contradict the 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 two sentences long, front-loaded with the key read-only nature, and conveys the exact purpose and usage context without any fluff. Every word contributes to understanding.

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 simple, parameterless tool with no output schema, the description fully covers the tool's role: it lists list names and IDs, is read-only, and provides a clear use case. The sibling list shows this is a distinct operation, and nothing critical is missing.

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 zero parameters, the schema coverage is effectively 100% and there is no parameter information to clarify. The description does not need to add parameter semantics, and the baseline of 4 for no-parameter tools is appropriate.

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 lists 'local Apple Reminders list names and IDs' with the specific verb 'list' and a defined resource. It distinguishes itself from sibling tools like apple_reminders_list (which lists reminders) and the create/update/delete tools by focusing on list names and IDs.

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 explicitly advises using this tool 'before creating reminders when the exact list name is unknown,' providing clear context for when to use it. It does not explicitly mention when not to use it or name an alternative, but the guidance is direct and useful for an agent.

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