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

With no annotations provided, the description carries the full burden of behavioral disclosure, but 'create CRM pipeline' only restates the obvious action. It does not mention side effects, required preconditions like an existing organization, validation behavior, idempotency, or what the response contains.

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 a single efficient sentence with no fluff, which is good, but it is also under-specified. It earns its place without wasted words, yet it is not sufficiently informative for the tool it describes.

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 tool with no annotations, no output schema, and several parameters, this description is too thin. It omits behavioral context, the meaning of stages, and return expectations, leaving the agent to rely almost entirely on the name and schema.

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 coverage is 67%, but the existing descriptions are unhelpful tautologies: 'name' and 'organization_id'. The tool description adds nothing about parameters, and the optional 'stages' array is left entirely unexplained. The schema provides structure, but the description does not compensate for the missing semantic detail.

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 'create CRM pipeline' names a specific verb and resource, and it clearly differentiates this tool from sibling pipeline tools like commsharbor_crm_pipelines_get, list, update, and delete. It is minimal but genuinely states what the tool does.

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 description offers no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. An agent has to infer from the tool name and sibling list that this is the creation action; there is no explicit context about when to choose create over update or delete.

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