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

It discloses the required permission (crm:read) and error semantics (404 for foreign or missing id), which is valuable context beyond the schema. Since no annotations are provided, the description carries the full burden and does it well, though it doesn't detail the return payload.

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 two sentences with zero wasted words. The core purpose is front-loaded, and the permission and error details follow logically without redundancy.

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 simple read operation, it covers permission and error cases, which is sufficient for calling the tool correctly. However, it doesn't mention the return format, and with no output schema, a note like 'Returns the pipeline object' would improve completeness. Still, it's largely adequate.

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?

The schema descriptions are merely the parameter names, adding no real meaning. The description adds no extra parameter details either, but schema coverage is 100%, 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?

The description states a specific verb ('Reads') and resource ('one pipeline') and clarifies it's from the tenant CRM. This clearly distinguishes it from list operations like commsharbor_crm_pipelines_list and other entity gets, making the purpose unambiguous.

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 implies singular use by saying 'one pipeline' but doesn't explicitly name alternatives or when to use the list sibling. It could benefit from stating 'For multiple pipelines, use commsharbor_crm_pipelines_list,' but the singular phrasing provides some guidance.

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