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

Beyond the readOnly/idempotent annotations, it adds the crucial behavioral fact that the tool 'opens nothing by itself' and only returns procedural guidance, plus the required follow-up surface (Cloud Browser). The closing note about Resource Guru's public REST API and read-only official MCP server gives useful context on why a browser path is needed, though it is somewhat tangential.

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 key behavior (returns instructions, opens nothing) is front-loaded in the first two sentences. The final sentence about the official API and MCP server, including a dated verification note, is context padding that does not help an agent select or invoke the tool.

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 zero-parameter guide tool with no output schema, it explains what the return value contains (screens, buttons, fields) and what to do next. It does not describe the guide's structure or scope limits (e.g., which booking views are covered), leaving 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?

Zero parameters, so there is nothing for the description to disambiguate beyond what the empty schema already conveys. Baseline 4 applies; no parameter-level detail is missing.

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 names a specific resource (bookings in Resource Guru) and then discloses the actual output: step-by-step instructions with screens, buttons and fields, not a data listing. This distinguishes it from an executor, since it explicitly hands execution to cotlet_browser_*. The leading verb 'List bookings' describes the user goal rather than the tool's effect, which is corrected only in the second sentence.

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 clearly routes the agent: call this to get instructions, then perform the action with cotlet_browser_* tools in the user's Resource Guru Cloud Browser. It does not state when not to use it or how it relates to the sibling resource_guru_* write tools (create_booking, add_time_off), which likely follow the same guide pattern but are not referenced.

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