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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds meaningful context beyond them: it returns a step-by-step procedure and opens nothing by itself, and it explains why browser automation is needed (Breezeway's API requires keys and there is no official MCP server). It does not describe output formatting, rate limits or authentication prerequisites in detail.

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 essential guidance is front-loaded: it returns a walkthrough and opens nothing itself, then execution moves to cotlet_browser_*. However, the final sentence about Breezeway's REST API and the checked date for lack of an MCP server is verbose and only tangentially relevant to assigning a task.

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, guidance-only tool with no output schema, the description says what the return contains (screens, buttons, fields) and how to follow up with browser tools. It omits prerequisites such as the user needing an active Breezeway session or what happens if they are not logged in, which would complete the picture.

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 has zero parameters, which establishes a baseline of 4. The description adds that the operation targets the user's own Breezeway account, implicitly confirming no credentials or task identifiers are supplied as arguments.

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 names a specific action and resource ('Assign task' in Breezeway) and makes clear this tool returns step-by-step guidance rather than performing the action, distinguishing it from write-oriented siblings like breezeway_create_task and breezeway_approve_task. It is not fully sharp about which task or how it is identified, but the core purpose 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 explicitly says to use this tool to get the screens/buttons/fields walkthrough and then execute via cotlet_browser_* tools in the user's Breezeway Cloud Browser, which gives clear context and a named alternative execution path. It stops short of explicit when-not-to-use conditions, such as when the user already knows the steps or when an API-based sibling should be preferred.

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