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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower; the description still adds real behavior: the api:chat scope requirement, newest-first ordering, the default row cap, and the 'truncated is true when more exist' signal. It does not mention pagination cursors or latency, but the disclosed traits are substantive.

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?

Dense single paragraph that front-loads scope, ordering, and auth before the field list, with no filler sentences. The enumerated return fields are long but each one is load-bearing since there is no output schema.

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 no output schema, the description documents the return shape field by field (id, title, source, symbol, mandate_id/case_id, category, timestamps) and explains the truncation flag, which is exactly what an agent needs to call and consume this tool correctly.

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 0%, so the description must carry the full burden and does: limit is bounded 1-200 with a default of 50, source narrows to a single surface (enum values web/api/telegram are defined in the schema), and include_archived adds archived conversations. Every parameter has meaning beyond its name and type.

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 with ownership scope ('YOUR conversations with your Gambit agent'), ordering (newest activity first), and an auth requirement. It distinguishes itself from get_conversation/manage_conversation by explaining that the returned id feeds those tools.

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?

Explains how each parameter selects behavior (source narrows to one surface, include_archived adds archived rows, limit caps rows) and routes follow-up calls to get_conversation/manage_conversation. It stops short of an explicit 'use this instead of X when Y' exclusion, so it is clear context rather than full when/when-not guidance.

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