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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, and the description is consistent with them ('opens nothing by itself'). It adds value beyond the annotations by disclosing the return content (screens, buttons, fields) and the required handoff to browser tools.

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 handoff are front-loaded and clear, but the closing sentence about Breezeway's REST API, request-form API keys, and the 'checked 20 Oct 2026' audit date is tangential to invoking this tool and dilutes focus.

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, read-only guidance tool with no output schema, the description covers what it returns, that it mutates nothing, and which tools to use next. It leaves implicit how the agent should locate the specific task in the browser, a minor 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, so the schema carries no semantics for the description to supplement; baseline is 4. It could have explained how the target task is identified (presumably via the browser session), but with no parameters there is little to document.

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 ('Reopen task in the user's own Breezeway account') and immediately clarifies the non-obvious twist that it returns step-by-step instructions rather than performing the action. It does not distinguish itself from close_task or the other breezeay_* task tools, so it is clear but lacks sibling differentiation.

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 an explicit usage path: call this for the walkthrough, then execute with the cotlet_browser_* tools in the user's Breezeway Cloud Browser. It also explains why the official REST API is not an alternative (API keys via request form, no official MCP server). No explicit when-not-to-use case is stated.

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