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

Annotations cover safety (readOnly, idempotent, non-destructive), so the description's added behavioral depth is notable: it explains per-channel reliability of last_outbound_seen, that 'inconnu' never means 'not read', how link vs link_readable behave, and that group participants are inferred from messages. This is exactly the operational nuance an agent cannot get from structured fields.

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?

Purpose and sort order are front-loaded, and the filter enumeration follows logically. The middle section on last_outbound_seen, links, and group participants is dense and reads as one long paragraph, which slightly hurts scannability, but every clause conveys real information.

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 an 11-parameter tool with no output schema, the description carries the return-shape burden well: it describes each item as a summary (name, channel, stage, tags, full last message), documents link/link_readable, last_outbound_seen values, and group vs direct shape. An agent has enough to call and interpret the result.

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 the baseline is 3 and the schema already documents all 11 parameters including enums and ranges. The description mostly restates the filter list; its only genuine addition is the cross-reference to ficiel_list_tags_and_stages for exact tag names, which is marginal value.

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 and resource (paginierte Liste der Konversationen der Organisation), the sort order (letzte Nachricht zuerst), and the scope (Direkt- UND Gruppengespräche). It also distinguishes itself from the detail view by noting each item is only a summary with detail in the full conversation, routing the agent to ficiel_get_conversation.

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?

Gives a clear context: it is the filtered, paginated listing tool and points to ficiel_list_tags_and_stages for exact tag names, and to the full conversation for detail. It does not explicitly contrast itself with ficiel_search or say when a listing is preferable to a search, so it falls short of the 5-level when/when-not/alternatives framing.

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