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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety bar is lower, but the description still adds genuinely new behavior: the call returns procedural guidance rather than performing the confirmation, and it acts in the user's own account. The API/MCP note explains why browser tools are required (the official API reads and writes but the MCP server only reads), which is real decision-relevant context.

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 behavior and the required follow-up are front-loaded in the first two clauses, which is exactly the right order. The trailing note on Resource Guru's public API and read-only MCP server is longer than it needs to be, and the 'checked 23 Oct 2026' provenance stamp is minor clutter, but the note does justify the browser-based approach.

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 covering the safety profile, the description carries the main burden of explaining what comes back, and it does so ('step by step (screens, buttons, fields)'). It is close to complete; it could add a word on what to do if the user's Resource Guru session is not authenticated, but that is a small gap.

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?

The tool takes zero parameters, which is the baseline-4 case; there is nothing for the description to disambiguate. The schema is empty with additionalProperties false, so no descriptive compensation is 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 action-and-resource: it returns step-by-step instructions (screens, buttons, fields) for confirming a tentative booking in the user's own Resource Guru account. Crucially it corrects the misleading name by clarifying that it 'opens nothing by itself', so an agent will not mistake it for a write action. It does not explicitly contrast itself with siblings such as resource_guru_approve_or_decline_booking.

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 follow-on workflow: call this, then act using the cotlet_browser_* tools in the user's Resource Guru Cloud Browser. What it does not say is when to prefer this over the other Resource Guru booking siblings, or what to do if the browser flow is unavailable. Usage is implied rather than delimited.

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