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

Annotations declare destructiveHint=true (mutation) and there are no other behavioral notes. The description says 'Create' which is consistent with a create operation, but it doesn't disclose what happens on duplicate leads, required permissions, or side effects. With annotations already carrying the mutation signal, the description adds almost nothing beyond API mapping.

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?

Two short sentences, front-loaded with the action and resource, no filler.

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 10-param create tool with nested objects and no output schema, the description is minimally adequate. It doesn't explain return values (no output schema), nor does it highlight required vs. optional beyond what the schema already shows. It is sufficient to call the tool but thin on context.

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?

Schema description coverage is 100%, so every parameter is documented in the schema. The description adds no parameter-level meaning beyond what is already in structured data. Baseline 3 is appropriate.

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 clear verb and resource: 'Create a new lead.' It also gives the underlying API endpoint, which helps an agent map to Copper's REST semantics. It doesn't explicitly distinguish from sibling creation tools, but the resource is unambiguous.

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?

The purpose implies use to create a lead, and the REST endpoint ties it to the Copper API. It does not specify when to choose this vs. sibling tools like copper_create_person or copper_create_opportunity, nor any prerequisites or constraints.

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