update-reminders

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description only adds that it's an update and to only send changed fields. It does not disclose error behavior (e.g., if a reminder ID doesn't exist) or mention array limits beyond the schema's maxItems.

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 clear, concise sentences. No unnecessary words. Front-loaded with action and key requirements.

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 complexity of the oneOf schema with many optional fields, the description is adequate for partial updates. It mentions the constraint of including type and ID. With an output schema present, return values are covered. Could mention that all reminders must exist for the operation to succeed.

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% with detailed descriptions. The description reinforces the requirement for type and ID and adds the guidance to only include fields that need to change, which is not in the schema. This adds value beyond the schema.

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 it updates existing reminders, specifies required fields (type and ID), and lists the three types. This distinguishes it from add-reminders (create) and find-reminders (read).

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 says 'Only include fields that need to change,' indicating partial update semantics. It implies use when modifying existing reminders, but does not explicitly state when not to use it or mention alternatives like add-reminders for creation.

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