list_reminders

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

With no annotations, the description carries the full behavioral burden. It communicates a read-style listing operation scoped to the authenticated user, so an agent can infer safety. However, it does not disclose output format, ordering, pagination, or whether all reminder states are included.

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 with no redundant wording. The key information—action, resource, and scoping—is front-loaded and every word contributes value.

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?

For a simple, zero-parameter list operation, the description is largely complete and gives an agent enough to select the tool correctly. The main gaps are the absence of an output shape description and no routing to sibling tools, but the low complexity of this tool makes those less critical.

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?

There are zero parameters and the schema covers all of them, so the baseline is 4. The description adds meaningful context by clarifying that the operation uses the authenticated user's identity rather than requiring explicit 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 uses a specific verb ('List'), a clear resource ('reminders'), and a scope ('for the authenticated user'). This distinguishes it from sibling tools like get_reminder, create_reminder, and delete_reminder, and from other list-type tools such as list_channels and list_files.

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 states what the tool does but gives no guidance about when to use it versus alternatives, such as get_reminder for retrieving a single reminder or search-style tools. There are no explicit conditions, exclusions, or when-not-to-use indications.

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