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

Annotations already declare destructiveHint=true, and the description adds only that a note lands in the item's history. It does not say what a status move destroys or overwrites (prior status, history entries), nor mention side effects like automation beyond what the schema's run_status_automation already documents.

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 with the core action first. The trailing 'LACRM: EditPipelineItem.' is a backend-method tag that adds little for an agent, a minor bit of waste.

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 no output schema, the description covers the action but omits return behavior (does it echo the updated item?) and any permission prerequisites. Schema covers inputs, so the gap is mostly around outcomes.

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 all four parameters are already documented, including the string-Uid guidance and the automation default. The description's only addition is the 'Prospect → Won' illustration of status_id, which is marginal.

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 (move) plus resource (pipeline item) and a secondary effect (annotate history), with a concrete status-transition example. It is distinguishable from lacrm_create_pipeline_item and lacrm_get_contact_pipeline_items, though it never names alternatives explicitly.

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?

No when-to-use or when-not-to-use guidance. The 'and/or' phrasing hints the tool does two things, but nothing tells the agent when to prefer this over lacrm_create_note for logging history or lacrm_create_pipeline_item for a new item.

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