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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: the tool opens nothing itself, it emits screen/button/field level instructions, and the actual action must be carried out via the browser tools. The closing note about Copper's REST API and lack of an official MCP server is informational rather than behavioral, so it does not lift the score higher.

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 contract (returns steps, does nothing itself, then use the browser tools) is stated early and earns its place. However the final sentence about Copper's official API and the absence of an MCP server, including a dated check, reads as justification trivia that does not help an agent select or invoke the tool. The middle clause is also a run-on that packs the return contents, the no-op guarantee and the handoff into one sentence.

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?

With no input parameters and no output schema, the description carries the burden of explaining the return value, and it does so concretely (screens, buttons, fields, step by step). It also names the prerequisite environment, the user's Copper CRM Cloud Browser, and the tool family that performs the action. What is missing is a note on what happens if the browser session is not already open or the user is not authenticated.

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 per the baseline this scores 4; there is no parameter semantics for the description to compensate for. The description correctly does not invent arguments a caller might wrongly try to supply.

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 (create a task in Copper CRM) but immediately reframes it: the tool 'returns how to do it ... step by step' and 'opens nothing by itself'. That clarification is essential and effective, since the name alone would suggest a write operation; an agent can tell this is a guide-generator, not a mutator. It falls short of 5 only because the create-vs-guide distinction requires a careful second read rather than being stated up front.

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 explicit follow-on guidance: 'then do it with the cotlet_browser_* tools in the user's Copper CRM Cloud Browser', which tells the agent exactly how this tool fits into the workflow. What it lacks is any when-not-to-use signal or any differentiation from the copper_crm_create_lead / convert_lead / log_activity siblings, which an agent choosing between Copper tools would want.

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