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

The destructiveHint annotation already flags this as a write, and the description adds the return shape ({ PipelineItemId }) plus the fact that item types include deals/leads and that the note appears in history. It does not disclose permission requirements, whether duplicate items are allowed, or that run_status_automation can fire automations, so it adds moderate value but not rich behavioral context.

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?

Front-loaded core action followed by the return value in two compact sentences with no filler. The trailing 'LACRM: CreatePipelineItem.' merely echoes the tool name and could be dropped.

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?

With no output schema, the description usefully states the return value, and the schema fully carries parameter semantics. What is missing is behavioral framing for a mutating tool with only a destructiveHint annotation - no mention of automation side effects beyond the schema's run_status_automation flag, permissions, or duplicate handling.

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% and each parameter is well documented in the schema itself (including the lacrm_list_pipelines provenance for pipeline_id and the string-Uid convention). The description only restates that the note is optional, adding nothing the schema lacks, so the baseline 3 applies.

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 ('Create a pipeline item... on a contact in a given pipeline and status') and enumerates the entity types (deal, lead), so the agent knows exactly what is produced. It does not explicitly contrast with the close sibling lacrm_update_pipeline_item, so it falls short of full sibling differentiation.

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 description implies usage (attach a pipeline item to a contact) but never states when to prefer this over lacrm_update_pipeline_item or lacrm_add_contact_to_group, nor any prerequisites such as needing valid pipeline_id/status_id from lacrm_list_pipelines. No exclusions or alternatives are named.

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