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

With no annotations, the description does carry part of the burden and does disclose that changes flow into the external CRM and warrant user confirmation. However, it leaves the most consequential behaviors unstated: whether omitted fields are left untouched or reset, whether a partial update can break existing mappings, and what the response contains.

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?

One dense paragraph, front-loaded with the field list and ending on the safety caution — nothing is filler. The leading label phrase is a fragment rather than a sentence, which slightly weakens the opening.

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 7-parameter mutation with a nested object, zero schema descriptions, and no annotations or output schema, the description covers field names but not the ambiguity an agent actually faces: merge vs replace semantics, field_mapping format, and the required provider choice.

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 0%, so the description must compensate, and it names every settable field including the pipeline_config sub-keys and points at the sibling tools that supply those IDs. It omits the required 'provider' parameter (kommo/hubspot) and never explains the key/value shape or expected identifiers in field_mapping.

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?

The description enumerates exactly which integration settings are configured (sync_conversations, sync_contacts, create_leads, auto_sync, pipeline_config, field_mapping) and scopes them to the external CRM, which separates it from internal siblings like crm_update_settings. The action verb itself is only implied by the title, since the body opens with the fragment 'What to sync and where:'.

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?

It gives a real prerequisite hint for pipeline_config values (from list_kommo_pipelines / list_kommo_users) and a caution to 'confirm with the user', which is genuine usage guidance for a mutation. It never says when to use this versus get_crm_integration, connect_crm_integration, or crm_update_settings, and does not say whether reading current settings first is expected.

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