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

Annotations already declare destructiveHint=true, so the write/mutating nature is covered. The description adds the meaningful detail that status movement and note-appending can be combined or done independently, plus the API operation name (EditPipelineItem). It does not disclose whether changes are reversible, permissions required, or that a status change may trigger automation unless the schema param is read.

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 sentences, front-loaded with the action and effect, with a minimal example. The trailing 'LACRM: EditPipelineItem.' is arguably redundant scaffolding but is compact and could aid API mapping. No wasted prose.

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 4-param mutation tool with a fully documented schema and a destructiveHint annotation, the description covers the two core operations adequately. The absence of an output schema is acceptable since no return value is promised. Minor gap: no statement about what happens to the item or side effects of status changes.

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 baseline is 3 and the schema already documents all four parameters thoroughly (including the string-typed Uid hints and run_status_automation default). The description only re-surfaces 'status' and 'note' without adding syntax or format detail beyond the 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+resource pair ('move a pipeline item to another status', 'add a note to its history'), so an agent immediately knows this mutates pipeline state. It also gives a concrete example (Prospect → Won). It does not name a sibling to differentiate from lacrm_create_pipeline_item or lacrm_get_contact_pipeline_items, however the verb 'update/move' versus 'create/get' is inherently distinct.

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 'and/or' phrasing implies this is the tool for both status changes and note additions, which is useful context. But there is no explicit when-to-use vs. when-not guidance, no prerequisites, and no mention of the sibling lacrm_create_note for note-only workflows. Usage is only implied.

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