List Reminder Lists

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

The description discloses the return fields (ID, title, reminder count, overdue count), adding clarity about behavior. Since there are no annotations, this information helps the agent understand what to expect. It does not state limitations or side effects, but as a read-only list operation, the coverage is sufficient.

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?

Two sentences: the first states the action, the second specifies the return fields. No filler, appropriately sized.

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?

With zero parameters and no output schema, the description fully covers the tool's purpose and expected return data, making it complete for an agent to use correctly.

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 baseline is 4. The description adds no parameter-specific information because none are needed.

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 'List all reminder lists' with a specific verb and resource. It also lists the return fields, distinguishing it from sibling tools like show-reminders (which likely shows reminders within a list) and create-list.

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 clearly indicates this is the tool for listing all reminder lists, providing context for when to use it. It does not explicitly mention alternatives or exclusions, but the simplicity of the operation makes the usage unambiguous.

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