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

readOnlyHint=true already establishes this is a safe read. The description adds one useful behavioral detail beyond the annotations — that results are 'grouped by pipeline' — but says nothing about pagination, ordering, or return shape.

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 core sentence is front-loaded and waste-free. The trailing 'LACRM: GetPipelineItemsAttachedToContact.' is an internal API name that adds little for an agent, a minor blemish.

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-only tool with one fully documented parameter, the description covers what it does and how results are grouped, which compensates for the absent output schema. Nothing critical for a correct call is missing.

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 single contact_id parameter (including the 'always pass it as a string' hint and its contact-or-company scope) is fully documented in the schema. The description's 'one contact or company' restates what the schema already says, adding no new meaning.

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+resource (get pipeline items attached to a contact/company) and the scope ('one contact or company'), so the agent can distinguish it from the broader lacrm_list_pipeline_items. It does not name that sibling explicitly, so differentiation relies on the reader inferring it.

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 phrase 'attached to one contact or company' implies the use case (fetch a single entity's items) versus a global list, but there is no explicit when/when-not guidance and no reference to lacrm_list_pipeline_items as the alternative. Usage must be inferred.

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