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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, providing strong safety coverage. The description adds the domain constraint that each calendar can have up to 5 reminders, which is not in annotations, but it does not discuss return format or edge cases. This adds modest value beyond annotations.

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 only two sentences, with the main purpose in the first sentence and a brief relevant domain note in the second. No redundant or filler content.

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 read-only tool with rich annotations and a single well-documented parameter, the description sufficiently explains purpose and a key behavioral constraint. It lacks an output schema, but 'all reminder configurations' implies a list return, making it complete for its complexity.

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 schema fully documents the calendarId parameter with 100% coverage, so the description adds no additional parameter-level meaning. The baseline of 3 is appropriate since the schema handles all parameter semantics.

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 'Get all reminder configurations for a calendar' with a specific verb and resource, scoped to a calendar. It distinguishes itself from sibling tools like get_calendar, get_calendar_overrides, and add/delete_calendar_reminder by focusing on reminder configurations.

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 implies the tool is for reading reminder configurations but does not explicitly mention when to use it versus alternatives like add_calendar_reminder or delete_calendar_reminder. There are no exclusion statements or named alternatives, so usage is implied but not directly guided.

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