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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds meaningful behavior beyond annotations: bulk support via ids, filterable by contact_id/entity_id/only_in_work, and the cross-channel conversation history scope. It does not contradict annotations and no annotation contradiction is present.

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?

The description is compact and front-loads the core purpose. The '[Flattened action: list]' line is helpful but the 'get (por id)' mention is unnecessary and slightly confusing given the sibling tool. The phrase 'É o diferencial do Kommo' adds some context but is somewhat promotional filler.

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 6 parameters and no output schema, the description should provide more operational detail. It covers the main behavior, filtering, and bulk support, but omits pagination semantics, the meaning of `page`/`limit`/`account`, and what the returned list contains structurally. It is adequate for basic selection but not fully complete for confident invocation.

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?

The input schema has no descriptions and 0% schema description coverage, so the description must compensate. It does partially: it explains the `filter` JSON keys (contact_id/entity_id/only_in_work) and that `ids` enables bulk execution. However, `page`, `limit`, and `account` receive no semantic explanation, leaving significant gaps for a 6-parameter tool.

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 clearly identifies the resource ('Conversas (talks) do inbox unificado') and the main verb ('list'), further reinforced by '[Flattened action: list]'. However, it muddies the purpose by mentioning 'get (por id)' when a separate sibling tool kommo_talks_get exists, so it does not fully distinguish itself from that sibling.

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 provides useful context: this lists unified inbox conversations from WhatsApp/Instagram/Telegram and can be filtered. But it gives no explicit when-to-use vs alternatives, such as 'use kommo_talks_get for a single conversation' or 'use kommo_events for event history'. Usage is implied rather than stated.

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