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

Annotations already establish readOnly/idempotent/no-destructive, and the description adds the crucial non-obvious trait that the tool performs no action itself and only returns instructions, plus that a separate browser session is needed. The API-availability note (Public API exists, no official MCP server) further explains why this indirect route is offered, though it doesn't describe the shape of the returned guide.

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 content is compact, but the opening clause "from ChatGPT, Claude or any AI agent" is promotional filler, and the second sentence packs three distinct ideas into semicolon-joined fragments. The most decision-relevant fact (it only returns instructions) should lead rather than follow a sentence implying it lists shifts.

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 supplies the essentials: what it returns (step-by-step screens/buttons/fields), that it has no side effects, and which tools to chain next. It would be stronger if it clarified that this is not a data-fetching call, which is the main remaining ambiguity.

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 and the description adds no parameter detail, which is appropriate at baseline 4. Nothing about inputs is left ambiguous because there are none.

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 first sentence says "List open shifts in the user's own Shiftbase account," which reads like an API listing call, but the second sentence reveals it actually "Returns how to do it in Shiftbase step by step" and "opens nothing by itself." The real verb (return a how-to guide) is buried after a misleading opener, so an agent skimming may misclassify it against the sibling shiftbase_list_shifts.

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 downstream workflow — after this, perform the steps with cotlet_browser_* tools in the user's Shiftbase Cloud Browser — which is genuinely useful routing. However, it never says when to choose this over shiftbase_list_shifts, nor what conditions make the browser-based path preferable to a direct API-backed listing.

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