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

With no annotations provided, the description carries the full burden of disclosing behavior. 'Get' implies a read-only operation, but the description does not explain what is returned, whether authentication is required, how errors are handled, or any side effects. This is minimal transparency.

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 short and contains no fluff, but it is under-specified. A single sentence that only repeats the resource name is concise in length but not in content, leaving important context about scope and behavior unstated.

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 output schema and no annotations, the description should state what the tool returns or what 'get' means in terms of response behavior. It does not mention return shape, data included, or any caveats. The two required parameters are clear from the schema, but the overall definition is incomplete for an agent invoking it blindly.

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 schema already documents both parameters. The description itself adds no semantic detail beyond the schema, but the parameter names 'pipeline_id' and 'organization_id' are self-explanatory in context. This meets the baseline for a get-by-ID operation.

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 ('get') and a specific resource ('CRM pipeline'), and the singular form distinguishes it from sibling 'commsharbor_crm_pipelines_list'. However, it does not explicitly say that it retrieves a single pipeline by pipeline_id, and it largely restates the tool name without adding detail.

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 gives no guidance on when to use this tool versus alternatives such as list, create, update, or delete. There is no mention of prerequisites, how it differs from the list operation, or any conditions that would make this tool the right choice.

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