book_appointment

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

With no annotations, the description fully carries the burden. It discloses the reminder side effect, validation constraints (free slot, working hours, grid alignment), and error behavior (returns nearest alternatives). It also mentions the confirmation return value, giving a complete behavioral picture.

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 well-structured: one-sentence summary, procedural guidance, validation constraints, parameter list, and example. Each section adds value and is front-loaded with the main purpose. No extraneous content.

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?

Despite no annotations, the description covers prerequisites, validation rules, side effects, parameter meanings, and an example. It is comprehensive enough for an agent to invoke the tool correctly, especially since an output schema exists to handle return values.

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 description coverage is 0%, so the description must compensate. It does so thoroughly: each parameter has a source or format explanation (e.g., patient_id from find_patient, starts_at in clinic-local ISO 8601, not UTC). An example further clarifies usage.

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 states a specific verb ('Book'), resource ('appointment'), and an additional side effect ('queue a reminder for 24 hours beforehand'). It clearly distinguishes from siblings like reschedule_appointment and cancel_appointment by focusing on new bookings.

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 explicit guidance: 'Call check_availability first', and explains how to handle taken slots by offering nearest alternatives. This tells the agent exactly when and how to use the tool, including a prerequisite step and error recovery.

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