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

With no annotations provided, the description carries the full burden, and it excels: it discloses no upfront payment, the locked slot, calendar invite sending, and the expected return value. It also instructs the agent on required customer interactions, going beyond a simple operation summary.

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 concise yet information-dense, with the core action front-loaded and supporting details neatly organized. Every sentence adds value—payment policy, return value, side effects, and required pre-checks—without redundancy.

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 tool with 7 parameters, no output schema, and sibling tools for related actions, this description covers the essential context: what it does, what it returns, what side effects occur, and what the agent must do before invoking. It is sufficiently complete for an agent to decide when and how to use it.

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%, with each parameter having a description, so the schema already handles parameter meaning. The description adds no extra parameter-level detail beyond what the schema provides, such as formatting or constraints, so a baseline of 3 is appropriate.

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 'Reserve a cleaning slot,' which is a specific verb+resource pair that clearly states the tool's function. It distinguishes itself from siblings (check_availability, check_booking_status) by focusing on the booking action and its side effects.

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 description provides clear context for when to use the tool: after gathering full details and confirming the booking preview. It doesn't explicitly name alternatives or say when not to use it, but the 'Always ask...' instruction implies a precondition rather than a contrast with sibling tools.

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