alexa_create_reminder

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

Beyond annotations (which only mark it non-readOnly, non-destructive, openWorld), the description discloses the confirmation behavior: a client prompt where supported, otherwise a two-phase preview/confirmToken round-trip governed by MCP_CONFIRM_MODE. This is exactly the operational context an agent needs before calling a mutating tool.

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?

Front-loaded with the core action and time formats, then the sibling routing, then the confirmation flow. Every sentence carries distinct information, with the confirmToken warning living appropriately in the schema rather than bloating the description.

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 mutating tool with no output schema, the description covers the critical unknowns: the mutual-exclusivity of the time inputs, the timezone resolution rule, and the exact confirmation protocol including the fallback token loop. Nothing needed to invoke it correctly is missing.

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%, so the baseline is 3, but the description adds real meaning: it frames 'at' vs 'inMinutes' as alternative time inputs (a relationship the schema does not express), and clarifies that the time resolves against the device's time zone rather than the caller's.

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?

States specific verbs and resources ('Set an Alexa reminder ... or an alarm on an Echo device') and explicitly distinguishes itself from a sibling by naming alexa_create_timer for the countdown case. An agent can separate this from other siblings without opening the schema.

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?

Explicitly routes the agent: use this for reminders/alarms, use alexa_create_timer for a countdown timer. It also states the time can be given two ways and that the time is applied in the device's own zone, so the selection conditions are clear.

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