reschedule_appointment

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

Discloses atomicity, the earlier-only safety check, and portal re-validation. Lacks details on failure modes, but covers key behaviors without 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?

Two sentences and one paragraph, front-loaded with purpose. Every sentence adds value, 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?

Output schema exists but not shown, so return values not needed. Description and schema together fully explain behavior and parameters for a 5-param tool.

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 baseline 3. The description adds context for `require_earlier` and `new_slot_date`, explaining their roles in the safety check and reporting.

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?

Clearly states 'Move an existing appointment to a different slot' with the atomicity qualifier. Distinguishes from siblings like 'book_appointment' and 'search_slots' by specifying rescheduling.

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?

Provides guidance on using `require_earlier` for unattended routines, implying a use case. Does not explicitly compare with siblings, but the context makes it clear.

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