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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this by explicitly stating 'Creates nothing and charges nothing itself.' It also discloses the return payload (price estimate, booking brief, link) which is beyond the annotations. This adds useful behavioral context without contradiction.

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 with no fluff. The purpose is front-loaded, and the inputs and outputs are concisely enumerated. Every sentence earns its place; this is exemplary structure.

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 lacking an output schema, the description fully explains what the tool returns (price estimate, booking brief, link) and the flow (human confirms and pays). It covers the key operational aspects, though it doesn't mention potential error cases or prerequisites beyond the required parameter. Given the annotations and schema richness, this is nearly complete.

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 the schema already documents all parameters. The description adds minimal semantic value, only paraphrasing a few inputs ('tutor id, how long, who it is for, optionally a preferred time'). It does not go beyond the schema's descriptions, so the 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 a specific verb and resource: 'Assemble a real tutoring booking,' and further defines its scope by clarifying it returns a price estimate, booking brief, and confirmation link. It clearly distinguishes from siblings (search_tutors, get_tutor) by focusing on the booking assembly step.

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 implies when to use it: after selecting a tutor, to prepare a booking for human confirmation. It provides context ('Assemble a real tutoring booking... to finish in one tap') but does not explicitly name alternatives or exclusions. Since siblings are all information-gathering tools, the usage context is clear enough.

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