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

Annotations declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with the crucial clarification 'opens nothing by itself' — resolving the apparent contradiction between the name 'cancel' and a read-only tool. It also discloses the response shape (screens, buttons, fields) and notes the API limitation is time-stamped, which is real behavioral context beyond the annotations.

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 core is front-loaded: what it returns, and that it opens nothing. The third sentence is long and packed with API/SDK detail, and 'from ChatGPT, Claude or any AI agent' is filler that does not help selection, though the API context does justify why the browser route is required.

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?

With no parameters, no output schema and annotations already covering safety, the description supplies everything an agent needs: what the call returns, that no side effect occurs, which tools perform the action, and why the API alternative is unavailable. Nothing required for correct invocation 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?

There are zero parameters, so the schema baseline of 4 applies and there is nothing further for the description to disambiguate. No parameter meaning is added or needed.

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 (cancel a reservation in the user's own PushPress account) and immediately clarifies that the tool returns step-by-step instructions rather than performing the cancellation. That second sentence is what separates it from pushpress_book_class_reservation and the cotlet_browser_* action tools, so an agent knows exactly what it gets back.

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?

It gives an explicit workflow: call this to get the steps, then execute them with cotlet_browser_* in the user's PushPress Cloud Browser. It also pre-empts the obvious alternative by explaining why the official PushPress Platform API/SDK is not the route (mostly read-only beyond customer and invitation creation), so the agent knows both the next step and the rejected path.

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