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

Annotations cover only destructiveHint=true, so the description's note about Copper-enforced required fields and the underlying REST endpoint adds some useful context. But it says nothing about side effects, duplicate handling, permissions, or what a successful call yields, leaving real gaps for a mutation 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?

Two short sentences, the purpose is front-loaded, and the requirement note follows. Nothing is padded or redundant.

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 ten parameters, no output schema, and only a bare destructiveHint, the description should say what is returned (e.g., the created opportunity id) and how the many optional fields behave. Instead it covers only the two required fields, which the schema already handles.

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 all ten parameters are already documented in the schema. The description's 'name and primary_contact_id are required' merely restates the required array and adds no format or default information beyond it.

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?

States a specific verb and resource ('Create a new opportunity (deal)'), which is enough to distinguish it from the other copper_create_* siblings by resource noun alone. It does not, however, explicitly route the agent away from related tools like copper_create_lead or copper_search_opportunities.

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?

No guidance on when to use this versus alternatives such as copper_create_lead, nor any prerequisite notes (e.g., checking for existing opportunities, needing a contact/company id first). It only asserts what Copper requires.

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