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

The only behavioral content is the REST endpoint (POST /companies), which is a minor implementation detail. The description says nothing about required permissions, duplicate handling, what happens on conflict, or what the call returns. The destructiveHint=true annotation is present but the description neither explains nor contradicts it, so the description carries almost no additional behavioral weight.

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 fragments with zero padding and the primary action front-loaded. It is efficient, though the endpoint fragment is arguably filler for most agents.

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 six-parameter mutation tool with no output schema, the description should at least indicate what is returned (e.g., the created company and its id) and any prerequisite such as authentication or duplicate-name behavior. None of that is present, leaving meaningful gaps.

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 six parameters (name, tags, details, assignee_id, email_domain, phone_numbers) are already documented in the schema. The description adds no format, constraint, or default information beyond that, so the baseline of 3 applies.

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 company") that clearly distinguishes it from copper_create_person, copper_create_lead, and copper_create_opportunity. It does not, however, explicitly contrast itself with sibling creation tools or search tools, so it is clear but not maximally differentiated.

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?

There is no guidance on when to use this tool versus alternatives - e.g., whether to call copper_search_companies first to avoid duplicates, or when to prefer copper_create_lead/copper_create_opportunity. The agent must infer usage entirely from the name.

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