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

Annotations declare idempotentHint, destructiveHint, and openWorldHint, but the description goes well beyond them: it discloses the server-side coverage recheck, the three outcome states (in_service_area, office_callback_requested, outside_massachusetts), that nothing is created outside Massachusetts, that no appointment is ever booked, and the 30-minute duplicate window. It also supplies caller-facing script content, which annotations cannot convey.

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?

Dense but well-structured: trigger condition first, then required inputs, then outcome branching, then the idempotency caveat. Every sentence carries operational information and nothing is padding.

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 a nested 5-parameter schema and a mutation side effect, the description covers the trigger, required inputs, all outcome branches, and duplicate behavior. An output schema exists, so return-value documentation is unnecessary, and nothing an agent needs to call or report back 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 description coverage is 100%, so the params are already documented, and the description's parameter content is mostly a restatement of the required list. It adds only the ordering nuance that confirmed:true must come after the caller agrees and that the ZIP drives the coverage and Massachusetts determination, neither of which is a large semantic addition.

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 a specific verb and resource ('Request Out-of-Area Office Callback') and immediately scopes it to callers outside the automatic-booking service area who agree to an office call. An agent can distinguish this from siblings like request_callback, check_service_area, or request_booking without opening a 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?

The first sentence gives an explicit trigger condition ('as soon as a caller is found to be outside the automatic-booking service area and agrees to a call'), and it routes the in-area case back to normal booking ('in_service_area means continue normal booking (no callback is created)'). This is explicit when-to-use and when-not-to-use guidance.

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