send_reminder

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

Given no annotations, the description carries the transparency burden. It discloses delivery channel: 'printed to the server log by default, or SMS when Twilio is configured.' Also notes manual trigger ahead of scheduled time. It does not mention error behavior, but that's acceptable for a simple send action.

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?

Five short sentences plus example; each sentence adds value. Front-loaded with primary action; no fluff.

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?

Tool is simple (one param, no annotations). Description covers purpose, when-to-use, delivery behavior, and examples. Output schema exists, so return format isn't needed. Adequate for an agent to select and invoke 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 provides only appointment_id as an integer with no description. The description compensates with an example call: 'send_reminder(appointment_id=12)' and contextualizes it as 'this appointment's reminder.' However, it doesn't elaborate on semantics beyond the parameter name, so it's helpful but not exhaustive.

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 opens with a specific verb and resource: 'Send this appointment's reminder now, ahead of its scheduled time.' It clearly distinguishes from the automatic process_due_reminders by stating routine reminders go out on their own.

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 states when to use: 'Use when a caller asks to be reminded again, or to confirm details in writing.' Also provides exclusion: 'Normal reminders go out on their own via process_due_reminders — you do not need this for routine bookings.' Names the alternative tool.

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