Reminders List Lists

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. However, the description adds no behavioral context—no mention of output, side effects, or scope. It merely frames the tool as a 'delegated Apple domain tool,' which is structural, not behavioral.

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, but it is wasted wording that does not explain the tool's function. This is under-specification rather than effective conciseness, similar to a placeholder statement.

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?

Even though the tool has no parameters and an output schema exists, the description fails the basic requirement of stating what the tool does. The name hints at listing reminder lists, but an agent has no way to know what a list is in Apple Reminders or how this differs from reminders_list_reminders. The definition is inadequate for correct tool selection and invocation.

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 and the input schema is an empty object, so schema coverage is effectively 100%. The description adds no parameter information, but none is required; the baseline of 4 for 0-parameter tools applies.

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 is a tautology: 'Delegated Apple domain tool reminders_list_lists exposed through Apple-Tools-MCP' restates the tool name and domain without stating what the tool does. There is no verb, no resource, and no differentiation from siblings like reminders_list_reminders.

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 offers no guidance on when to use this tool versus alternatives. It does not reference sibling tools such as reminders_list_reminders, reminders_get_reminder, or apple_suggest_reminder_lists, so an agent cannot determine the appropriate context for selection.

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