list_reminders

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

No annotations provided, and the description does not disclose whether the operation is read-only, has side effects, or requires permissions. A simple 'list' implies read-only, but no explicit confirmation.

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 very short (4 words), which is concise, but it omits crucial information about the missing parameter. Conciseness is not helpful if it misleads.

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?

Given the lack of output schema and the discrepancy between description and schema, the description is incomplete. It fails to clarify what reminders are listed (e.g., all reminders across all lists? but says 'from a specific list' without a way to specify).

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 description mentions 'a specific list' but the input schema has zero parameters, creating a contradiction. The description adds misleading meaning beyond the schema by implying a parameter that does not exist.

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 name 'list_reminders' is clear, but the description 'from a specific list' is ambiguous because the input schema has no parameter to specify which list. It doesn't distinguish from sibling 'list_reminder_lists' which likely retrieves the lists themselves.

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?

No guidance on when to use this tool versus alternatives like 'list_reminder_lists' or 'create_reminder'. The description does not clarify prerequisites or context.

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