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

Annotations already declare readOnlyHint=true, openWorldHint=false, idempotentHint=true and destructiveHint=false, and the description reinforces this with 'opens nothing by itself'. More valuably, since there is no output schema, it discloses the return content (a step-by-step walkthrough of screens, buttons and fields) and the follow-up dependency on browser tools. It says nothing about authentication state or what happens if no browser session is open.

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 is front-loaded and easy to parse, but the closing tangent about Breezeway's official REST API and the 'checked 20 Oct 2026' note is justification padding that an agent does not need in order to invoke the tool. It could be compressed to the essential two clauses.

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 full annotation coverage, the description supplies everything needed: what it returns, that it performs no action, and which tools to chain afterward. The only minor gap is not specifying the response format of the step-by-step output, which matters somewhat given the absence of an output schema.

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 there is nothing for the description to disambiguate. Baseline 4 applies; the description correctly implies no scoping inputs are needed.

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 states a specific verb and resource (list tasks in the user's Breezeway account) and clarifies the actual output is step-by-step how-to guidance rather than task data. It does not differentiate itself from sibling list tools such as breezeway_list_people or breezeway_list_properties, but the resource is unambiguous.

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 operating sequence: call this to get screens/buttons/fields, then perform the action with cotlet_browser_* tools in the Breezeway Cloud Browser. It also explains why this route exists (Breezeway's REST API needs API keys from a request form and has no official MCP server), implicitly justifying it over a direct API call. It stops short of explicit when-not-to-use conditions.

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