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

Annotations already declare readOnlyHint=true and non-destructive/idempotent, and the description adds the crucial behavioral fact that it 'opens nothing by itself' and returns procedural steps. It also scopes the target to the user's own account, which is meaningful access context, though it does not describe the return payload's size or format 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 action description and the 'opens nothing by itself' caveat are front-loaded, which is the right order. The trailing note about Freshsales' official REST API and lack of an official MCP server, including a checked date, is somewhat tangential and could be trimmed.

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, no-output-schema guidance tool, the description covers what it returns, what it does not do, and which tools to use next. The remaining gap is that it does not quantify the guidance output or mention any account-permission prerequisites.

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 parameter burden and the baseline is 4. The description correctly implies no input is needed before returning guidance.

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 verb and resource ('Add note in Freshsales') and clarifies that the tool returns step-by-step instructions rather than performing the action. This disambiguates it from the cotlet_browser_* action tools, though the 'add_note' name still implies a write, creating minor friction resolved only by reading the body text.

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 routes the agent: get the guide here, then execute with cotlet_browser_* in the user's Freshsales Cloud Browser. It does not name a competing Freshsales MCP alternative or state explicit exclusions, but the intended usage chain is clear from context.

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