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

With no annotations, the description carries the full burden of behavioral disclosure, but it only says 'create CRM company.' It does not mention side effects, duplicate handling, idempotency, permissions, or response behavior. This is minimal transparency for a mutating operation.

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 description is extremely concise and wastes no words, with the core action front-loaded. It is arguably too terse for the complexity of the tool, but as a conciseness measure it is efficient and free of 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?

The tool has four parameters, two required ones, no annotations, and no output schema, yet the description only says 'create CRM company.' It omits what organization_id refers to, how domain and website relate to the company, and what the caller should expect after creation. An agent can guess the basic action but lacks enough context for confident invocation.

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 the baseline is 3 even without parameter details in the description. However, the schema descriptions are mostly tautological ('name', 'domain', 'website', 'organization_id'), adding little real semantic value. The description contributes no additional parameter-level meaning.

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 CRM company.' The intent is unambiguous and distinct from sibling update/list/delete operations on companies. It does not explicitly contrast with sibling create tools, but the resource type is specific enough.

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 such as commsharbor_crm_companies_update or commsharbor_crm_companies_list. It also does not mention prerequisites, such as needing an existing organization_id, or any related workflow context. The agent must infer usage entirely from the tool name.

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