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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds a genuinely useful, non-obvious behavioral rule: an empty status filter returns items in all ACTIVE statuses (not all statuses). It stops short of describing pagination or result shape, keeping it below a 5.

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 tightly packed sentences with the core operation front-loaded and no filler. The trailing 'LACRM: GetPipelineItems' marker is low-cost but slightly extraneous phrasing in an otherwise efficient definition.

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 an 8-parameter list tool with no output schema and only a readOnlyHint annotation, the description is barely adequate. It covers the status-filter edge case but is silent on pagination behavior, default sort, and how advanced_filters compose, even though the schema carries the parameter-level detail.

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 every one of the 8 parameters is already documented in the schema and the baseline is 3. The description adds only the semantic that an empty status_ids filter means 'all active statuses'; it adds nothing for page, sort_by, sort_direction, max_results, or advanced_filters.

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?

States a specific verb and resource ('List the items in one pipeline') and clarifies the domain with examples (deals, leads...). It does not explicitly distinguish itself from the nearby siblings lacrm_get_contact_pipeline_items or lacrm_list_pipelines, which would have pushed it to a 5.

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?

It states the optional narrowing dimensions (statuses, users) and the empty-filter behavior, so usage is implied. However, it never says when to prefer this over the contact-scoped or pipeline-list siblings, and offers no stated prerequisites beyond the schema's reference to lacrm_list_pipelines.

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