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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, but the description adds the critical fact the annotations cannot convey: this call performs no action and returns procedural guidance (screens, buttons, fields) that must be executed via browser tools. That prevents a false expectation of returned timesheet records. It stops short of describing the exact response shape or whether the guidance is account-specific.

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 purpose and the 'opens nothing by itself' caveat are front-loaded and useful, but the trailing sentence about Shiftbase's Public API and the dated 'no official MCP server (checked 22 Oct 2026)' note is justification/marketing material that does not help an agent decide or invoke. The mid-sentence pivot ('then do it with the cotlet_browser_* tools') is also awkwardly embedded.

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 and no output schema, the definition covers what an agent needs: what it returns, that it is non-acting, and which tool family to use next. Minor gaps remain, such as whether the Shiftbase browser session must already be open and whether the guidance is scoped to a particular account or date context.

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 schema has zero properties, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. The description correctly implies no input is required before use.

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?

States a specific verb and resource ('List timesheet entries in the user's own Shiftbase account') and immediately clarifies the non-obvious mechanic: it returns step-by-step instructions rather than data. That distinguishes it from an ordinary read tool. It does not explicitly contrast with close siblings such as shiftbase_list_shifts or shiftbase_list_open_shifts, leaving the resource boundary to the names.

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?

Gives real workflow guidance: the tool 'opens nothing by itself' and the actual action must then be performed 'with the cotlet_browser_* tools in the user's Shiftbase Cloud Browser.' However, there are no when-not conditions and no explicit routing against the other shiftbase_* listing tools, so the agent must infer which listing tool applies.

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