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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true), it discloses the required scope `bookings:write`, that the first call is a no-op dry run, and that invalid fields are rejected by name. That is meaningful context the annotations do not convey. It stops short of saying what the second call returns or how failures behave.

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?

Three short sentences, front-loaded with the purpose and then the two-call protocol in the order the agent needs it. Dense but nearly every clause carries operational information; the phrasing is slightly compressed but not wasteful.

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 mutating, non-idempotent, open-world tool with no output schema, the description covers the authorization requirement, the two-phase confirmation flow, and validation behavior. The notable remaining hole is the meaning and format of the required `rating` parameter, which nothing else in the definition supplies.

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 only 33%, and `rating` is declared with no type and no description anywhere, so the agent gets no help on its expected form or range. The confirm_token lifecycle is explained well, but that value is already documented in the schema, so the net gain over structured fields is modest.

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?

"Review a completed booking" gives a specific verb and resource, and the body clarifies the operation is a rating submission tied to a proposal_id. It does not explicitly distinguish itself from siblings like list_pending_reviews or get_review_summary, so an agent must infer that this is the write-side action.

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 gives unusually concrete usage guidance: call once with no confirm_token, show the returned summary to the person, and only call again after they agree. What it lacks is a statement of when to choose this over sibling review tools, but the procedural conditions are explicit.

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