list_reminder_lists

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

With no annotations, the description carries the full burden of behavioral disclosure. It states that the tool lists all reminder lists, which implies a read-only operation, but it does not disclose any additional behavioral traits such as whether hidden lists are included, if any permissions are needed, or how results are ordered. This is adequate for a simple zero-parameter tool but lacks depth.

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, complete sentence that is front-loaded with the action and object. It contains no fluff or redundant information, making it highly concise and well-structured.

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 tool's simplicity (zero parameters, clear purpose), the description fully covers what the tool does. An output schema exists to describe return values, so the description does not need to explain those. It is contextually complete for its scope.

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?

The tool has zero parameters, so the input schema adds no information. The baseline for 0 params is 4, and the description does not need to add parameter-level semantics. It correctly focuses on the tool's action rather than parameter details.

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 a specific verb ('List'), resource ('reminder lists'), and context ('macOS Reminders app'), and it distinguishes itself from sibling tools that operate on individual reminders (e.g., list_reminders, create_reminder). It is unambiguous and informative.

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. It does not explicitly state that this is for obtaining list metadata or IDs before working with reminders, nor does it contrast with list_reminders. The usage is only implied by the tool's name and purpose, offering no exclusion criteria.

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