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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and the description is consistent with them, adding the important fact that it "opens nothing by itself." It does not describe the shape or granularity of the returned step-by-step guide (how many steps, whether it covers validation errors or required fields), so the added behavioral context is useful but thin for a tool whose entire output is prose instructions.

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 critical constraint ("opens nothing by itself") is front-loaded in the first sentence, before the follow-on tool guidance. The trailing sentence about Copper's REST API and the "checked 20 Oct 2026" date is tangential justification rather than operational information, costing it a point.

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 tool the description covers the essentials: what it returns, that it has no side effects, and which tools continue the workflow. It omits how the target lead's field values are supplied and what the returned guide looks like, which an agent needs to sequence the call 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?

Zero parameters gives a baseline of 4, but the absence of parameters raises a real question the description never answers: how the agent communicates which lead to create (name, company, email) given there is no input object. The description does not explain that lead details must come from conversation context, leaving a semantic gap around an otherwise empty schema.

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 uses a specific verb+resource ("Create lead in the user's own Copper CRM account") and then clarifies the actual mechanism: it "Returns how to do it in Copper CRM step by step." That resolves the tension between the name and the read-only behavior, though the dual framing (creates vs. returns instructions) makes the agent read twice to understand what it really gets back.

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 states the follow-on path explicitly: "then do it with the cotlet_browser_* tools in the user's Copper CRM Cloud Browser," which tells the agent what to do after calling. It does not distinguish this from sibling operations like copper_crm_convert_lead or copper_crm_log_activity, so the agent gets clear context but no exclusions.

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