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 adds two useful pieces of context: it performs no side effects ('opens nothing by itself') and it returns step-by-step screen/button/field guidance. The API/MCP-availability sentence is informational but does not change how the agent calls the tool.

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 behavioral fact (returns instructions, acts on nothing) is buried in the second sentence rather than front-loaded, and the closing sentence about Copper's official API and MCP server status is tangential to invoking the tool. It is not bloated, but the ordering makes the true function easy to miss.

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 zero parameters, no output schema, and rich annotations, the description carries a light burden, and it does disclose the return shape at a high level and the follow-up browser workflow. The remaining gap is that it never clearly states whether the return is pipeline records or procedural guidance, leaving the agent's expectation of the result ambiguous.

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 baseline is 4. The description adds nothing parameter-related because there is nothing to disambiguate, and the empty schema is self-explanatory.

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 opens with 'List pipelines in the user's own Copper CRM account,' which is a specific verb+resource, but the second sentence reverses that expectation: the tool 'Returns how to do it in Copper CRM step by step (screens, buttons, fields) and opens nothing by itself.' An agent must reconcile whether this returns pipeline data or instructions for retrieving it, which undercuts the otherwise clear naming.

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 a usable workflow cue: the tool opens nothing and you should then act via the cotlet_browser_* tools in the Copper CRM Cloud Browser. However, it does not name any sibling alternative (e.g. copper_crm_list_opportunities) or state when to prefer this over a direct data-listing path, leaving the routing decision implied rather than explicit.

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