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

Annotations already declare readOnly/non-destructive/openWorld, so the safety profile is covered. The description adds useful non-annotation context: ordering ('most recent first'), pagination mechanics via next_cursor, and an auth requirement (Cotlet API key with access to this app).

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-loads the core action and item shape, and every sentence carries information. Mild redundancy in re-stating 'Immobiliare.it' and 'Conversations in Messages' at the start, which slightly dilutes tightness.

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?

No output schema exists, so the description responsibly describes the returned item shape (listing, other person, last message, visit-request flag) and the pagination cursor. Enough for correct invocation, though it omits total-count or empty-result behavior.

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 coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema for cursor ('Pass next_cursor back as cursor for the next page') and clarifies the listing_id filter intent. limit has no added explanation but is fully documented in-schema.

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 ('Lists conversations in Messages'), plus content of each item and ordering ('most recent first'). This clearly separates it from sibling immobiliare_get_conversation, but the description never explicitly names a sibling to anchor the contrast.

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?

Offers conditional guidance for the listing_id filter ('only the people who wrote about one listing') and a pagination instruction, but gives no explicit when-to-use-this-vs-get_conversation routing and no prerequisites beyond the auth note.

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