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

The readOnlyHint annotation already establishes this as a safe read, lowering the burden on the description. The description adds a genuinely useful behavioral detail — results are grouped by pipeline — but says nothing about pagination, ordering, result volume, or empty cases. With annotations covering safety, this is a modest value-add.

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, front-loaded sentences that get to the point immediately. The trailing 'LACRM: GetPipelineItemsAttachedToContact' largely restates the tool name, which is mild redundancy, but overall it is tight and well-structured.

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 single-parameter read tool with safety covered by annotations, the description is close to sufficient, and 'grouped by pipeline' gives a hint about the return shape. However, with no output schema, it could have described the returned item structure more concretely. Adequate but with a clear gap.

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%; the contact_id parameter is fully documented in the schema, including the string-format nuance ('always pass it as a string'). The description only echoes 'one contact or company' without adding syntax or format detail. Baseline 3 applies when the schema does the heavy lifting.

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 names the specific resource (pipeline items) and pins its scope to 'one contact or company,' which implicitly separates it from the sibling lacrm_list_pipeline_items. It adds the useful output-shape detail 'grouped by pipeline.' It stops short of naming the sibling or explicitly contrasting the two, so it is clear but not fully 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 when-to-use/when-not guidance and no mention of the obvious alternative lacrm_list_pipeline_items or lacrm_list_pipelines. An agent must infer from scope alone that this is the contact-scoped variant. No prerequisites or exclusions are given.

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