reminder_lists

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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description adds genuinely new context: it requires EventKit (Reminders) access, i.e., an authorization prerequisite. That is useful beyond what annotations convey, though rate limits and pagination are not covered.

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?

Three compact clauses, front-loaded with what it does and what the output looks like. Every element (pointers, folder mapping, read-only, auth, write alternative) carries information an agent needs.

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?

An output schema exists, so return-value detail isn't strictly required, yet the description still explains the pointer shape and its relation to reminders. Combined with the auth note and the write-routing hint, nothing essential is missing for a zero-param 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?

The tool takes zero parameters, so the baseline is 4. The description appropriately uses its space to explain the meaning of the values returned (id/name, and that id equals the reminder 'folder') rather than inventing parameter detail.

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?

States a specific verb and resource ("List reminder lists") and even the return shape: "pointers (id + name)". It further disambiguates by explaining 'id' is the 'folder' reminders carry and by naming create_reminder for the write path, so an agent can tell it apart from sibling reminder tools.

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?

Gives a clear usage rule ("use a name to target writes") and routes to the correct alternative ("See create_reminder to write"). It doesn't spell out when-not conditions, but the read-before-write context is explicit enough.

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