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; the description reinforces rather than contradicts them by stating the tool opens nothing and only returns text. It adds genuinely useful context beyond annotations: the required follow-up browser tools and the fact that no official MCP server exists, explaining why browser automation is the path. Return-format detail beyond "step by step" is absent.

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 workflow and the "opens nothing by itself" clarification are front-loaded and useful. However, the closing sentence about Copper's REST API and MCP server status, plus the "from ChatGPT, Claude or any AI agent" framing, is marketing-adjacent and only loosely earns its place, even if it justifies the browser route.

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 guide tool, the description covers what it returns, what it does not do, and which tools to use next. The only gap is that it does not characterize how detailed or how long the returned steps are, which mildly affects planning.

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 schema has zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly presents this as a no-input guide call.

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 makes clear this is a guide-producing tool rather than a mutating one: it "Returns how to do it in Copper CRM step by step (screens, buttons, fields) and opens nothing by itself." That distinguishes it from the cotlet_browser_* action tools and from copper_crm_create_lead. It loses a point because the leading verb "Convert lead" and the title imply an action, so the agent must read past the first clause to learn the tool only returns instructions.

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 an explicit two-step workflow: call this to get the procedure, then execute it with cotlet_browser_* in the user's Copper CRM Cloud Browser. It also states what the tool will not do ("opens nothing by itself"), which prevents misuse. It stops short of saying when not to use it or naming a specific browser sibling to start with.

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