find-reminders

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds behavioral context that taskId returns both time-based and location reminders, and clarifies the distinction between the two reminder ID types. This goes beyond the structured annotations without contradicting them.

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 two concise sentences, front-loaded with the primary function and immediately explaining parameter usage. Every sentence earns its place with no wasted words.

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 simple schema (3 optional parameters), the presence of an output schema, and read-only/idempotent annotations, the description fully covers the tool's behavior. It explains both retrieval modes sufficiently for an agent to select and invoke the tool 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?

Schema coverage is 100% — each parameter already has a detailed description in the input schema. The tool description largely restates the same information (e.g., reminderId for time-based, locationReminderId for location), adding no new semantic detail beyond what the schema provides. Baseline 3 is appropriate.

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 the tool's function: finding reminders either by task ID (returning all reminder types) or by specific ID. It explicitly distinguishes between time-based and location reminders, making the resource and action unambiguous. This differentiates it from sibling mutation tools like add-reminders and update-reminders.

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 gives concrete parameter-selection guidance: use taskId for all reminders of a task, reminderId for time-based reminders, and locationReminderId for location reminders. It does not explicitly name alternative tools or exclusions, but the usage context for a read-only find operation is implied and clear.

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