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

readOnlyHint=true already covers the safety profile, and the description adds genuinely non-obvious behavioral context: an empty status filter returns items in all ACTIVE statuses, plus the underlying LACRM endpoint name (GetPipelineItems). It does not cover pagination behavior, but the annotations carry the important safety signal.

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 sentences, no filler, with the scope statement front-loaded and the non-obvious empty-filter rule immediately following. Every clause earns its place.

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 read-only list tool with a fully documented 8-parameter schema and no output schema, the description covers scope and a key filter subtlety. It leaves pagination and result-shape expectations to the schema, which is reasonable given the parameter descriptions handle those.

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 all eight parameters including page, sort, filters, and pipeline_id. The description's only added semantic is the empty-status-filters behavior, which is useful but marginal against a fully documented schema.

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 (List) and resource (items in one pipeline) and clarifies the item types with examples (deals, leads...). It reads clearly against lacrm_list_pipelines, though it doesn't explicitly name sibling list tools like lacrm_get_contact_pipeline_items as alternatives.

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?

Gives the useful filter conditions ('optionally only in given statuses or for given users') and the empty-status semantics, but offers no explicit when-to-use vs when-not guidance relative to the sibling tools that also return pipeline items (lacrm_list_pipelines, lacrm_get_contact_pipeline_items).

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