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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds the non-obvious behavioral fact that it 'opens nothing by itself' and only returns a procedure rather than records, which is exactly the kind of context annotations cannot express. The closing sentence about Freshsales' REST API and MCP server availability is meta-trivia that adds noise rather than behavioral clarity.

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 operative content (returns a step-by-step procedure, then act via cotlet_browser_* tools) is stated up front, but the sentence is long and parenthetical-heavy, and the final API/MCP-status sentence does not help an agent invoke the tool. It could be halved without losing anything actionable.

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 tool with no output schema, the description gives a reasonable sketch of what comes back ('screens, buttons, fields') and where it is then executed. It omits how to handle a missing browser session and whether 'rotten' is a fixed Freshsales filter or something the agent must configure, which an agent would need to act correctly.

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 a closed empty object, so there is nothing for the description to disambiguate. Baseline 4 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 description names the concrete task (listing rotten deals in Freshsales) and, crucially, clarifies that the tool does not fetch the data itself but returns step-by-step instructions (screens, buttons, fields) for the agent to follow. That resolves what would otherwise be a misleading name. It stops short of distinguishing itself from the many other freshsales_list_* siblings beyond naming the cotlet_browser_* tools as the execution path.

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 does say how the tool fits into a workflow: get the instructions here, then perform the work with cotlet_browser_* tools in the user's Freshsales Cloud Browser. However, it gives no guidance on when to prefer this over other Freshsales listing tools or cotlet_app_guide, and no prerequisites such as whether a browser session must already be open.

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