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

Annotations already declare the tool is not read-only, not idempotent, open-world, and destructive. The description adds meaningful behavioral context by noting optional customer confirmation emailing and that the booking 'Waits for the owner's approval.'

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 concise sentences front-load the core action and then add the optional email and approval workflow. There is no redundant or filler text.

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 destructive, open-world appointment-booking tool, the description covers the key approval workflow and optional customer email, while the schema fully documents all parameters. It does not explain conflict handling or return behavior, but no output schema exists and annotations carry the safety profile.

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 all seven parameters are already documented in the input schema. The description only reinforces 'staff' and the optional customer email, without adding new syntax or constraints beyond the schema.

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 and resource: 'Book a job appointment on the Scheduler for staff.' It also clarifies optional customer email and owner approval, making the action distinguishable from list_appointments and create_job.

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?

Usage is implied by 'Book a job appointment' and 'for staff,' but the description gives no explicit when-to-use guidance, no exclusions, and does not point to alternatives such as list_appointments for checking existing bookings.

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