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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, and the description adds genuinely new context on top: the tool "opens nothing by itself," it returns procedural steps, and the actual action must be performed with separate browser tools. It also discloses that Shiftbase has a public API but no official MCP server, which explains the workaround. It stops short of describing the shape or length of the returned steps, so a 4 rather than 5.

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?

Three sentences, but the most important fact -- that this returns instructions rather than shift data -- is buried mid-second-sentence after an overstated lead. The audience clause ("from ChatGPT, Claude or any AI agent") is promotional filler, and the trailing API/MCP-server note with a dated check is tangential to invocation, though it does explain the design.

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 full annotation coverage, the definition supplies the workflow context an agent needs. The residual gap is the unresolved ambiguity between "List shifts" and "returns how to do it," which could lead an agent to present instructions as if they were retrieved shift records.

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 schema is empty, so there is no parameter meaning for the description to add. Baseline for a parameterless tool applies.

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 opening verb+resource ("List shifts in the user's own Shiftbase account") reads like a data-fetch tool, but the second sentence reveals the tool does not list anything: it "Returns how to do it in Shiftbase step by step (screens, buttons, fields) and opens nothing by itself." That is a meaningful divergence between the name/lead claim and the actual function, so an agent must read the whole description to learn what the tool really produces.

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 real workflow directive -- call this first, then execute with cotlet_browser_* tools in the user's Shiftbase Cloud Browser -- which is more than most definitions offer. However, it offers no guidance on when to choose this over sibling listing tools such as shiftbase_list_open_shifts or shiftbase_list_timesheet_entries, leaving scope selection to be inferred from the resource noun alone.

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