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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description usefully adds that no browser action is performed by this call and that the user's own Avantio account/browser session is involved. The closing sentence about Avantio's official APIs and absence of an MCP server explains why the tool exists but adds little to invocation behavior.

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 first two sentences are front-loaded and earn their place, describing the return value and the follow-up browser workflow. The trailing 'Avantio's official API...' sentence is justification/marketing context that does not help an agent select or invoke the tool, and it dilutes an otherwise tight definition.

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 output schema, the description correctly tells the agent what comes back (UI steps) and what to do next (browser tools). But for a tool named 'get booking' with an empty input schema, the definition never resolves how the specific booking is targeted, leaving an important ambiguity for a complex multi-step workflow.

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 and schema coverage is 100%, so the baseline would be 4. However, a 'get booking' tool with no booking identifier or filter parameter is conspicuously unexplained — the description never says how the target booking is determined or whether the returned guide is generic. That unanswered question is a real semantic gap.

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 makes the real behavior explicit: it returns a step-by-step how-to for getting a booking in Avantio (screens, buttons, fields) rather than the booking record itself, and states 'opens nothing by itself'. That corrects the misleading 'get booking' name. It stops short of naming a data-returning sibling such as avantio_list_bookings, so the differentiation is implied rather than stated.

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 a clear usage path: call this to learn the Avantio UI steps, then execute them with the cotlet_browser_* tools in the Avantio Cloud Browser. It also implicitly excludes expecting data back ('opens nothing by itself'). It does not state when an agent should prefer a direct listing tool over the browser route.

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