Reminders List Reminders

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

Annotations declare readOnlyHint and idempotentHint, and the description does not contradict them. However, the description adds no behavioral context such as default include_completed=true behavior, filter semantics, or what kind of results are returned.

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 one short sentence, but it is uninformative boilerplate that repeats the identifier. It is under-specified rather than genuinely concise, and the single sentence carries no useful information.

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?

Despite having an output schema and annotations, the description omits the core action, purpose, and parameter meaning. An agent choosing among a large set of reminder and Apple tools would receive no contextual help from this definition.

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% across 6 parameters, and the tool description does not mention limit, search, list_id, due_after, due_before, or include_completed. The description fails entirely to compensate for the undocumented parameters.

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, 'Delegated Apple domain tool reminders_list_reminders exposed through Apple-Tools-MCP,' merely echoes the tool name and title without stating a verb, resource, or outcome. An agent cannot learn from the description itself that this tool lists 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?

There is no guidance about when to use this tool or how it differs from alternatives like reminders_get_reminder, reminders_list_lists, or reminders_create_reminder. The description provides no selection context or exclusions.

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