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

Annotations already declare destructiveHint=true, so the safety profile is partly covered. The description adds a genuinely useful behavioral detail absent from structured fields: the return value '{ PipelineItemId }', which matters since there is no output schema. It does not, however, explain side effects such as status automations beyond what the schema already states.

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 core action, and every clause earns its place: the domain clarification, the input context, the optional note, and the return shape.

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 create tool with full schema coverage, destructiveHint annotation, and no output schema, the definition is nearly complete—it even supplies the return value. A brief note on the automation side effect or that pipeline IDs come from lacrm_list_pipelines would make it fully self-contained.

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 every parameter is fully documented (including the string-encoded Uids and the run_status_automation default). The description only loosely maps concepts ('given pipeline and status, with an optional note'), which is the correct baseline 3 when the schema does the heavy lifting.

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') plus the parent context ('on a contact in a given pipeline and status'), and clarifies the domain term with 'deal, lead...'. It clearly reads as the creation counterpart to lacrm_update_pipeline_item, though it never names that sibling 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?

The description implies the setup inputs (a contact, a given pipeline and status) but gives no explicit when-to-use/when-not or routing guidance against siblings like lacrm_update_pipeline_item or lacrm_get_contact_pipeline_items. Usage is only implied through the 'Create' verb.

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