export_all_conversations

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

Annotations already cover safety (readOnly, idempotent, non-destructive), so the description wisely spends its words on what annotations can't express: the paid-workspace gate and quota consumption. Pagination contract (cursor/nextCursor/hasMore) is also disclosed, which is real behavioral context. It stops short of stating rate limits or whether the export is synchronous vs job-based.

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 verb and resource, then preconditions, then pagination/model, then formats. No filler sentences; each clause carries a distinct constraint.

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 usefully names the response keys (cursor/nextCursor/hasMore) an agent must read to paginate, plus formats and the free/paid gate. It leaves open what a record contains and whether large exports are chunked beyond the page limit, but is otherwise sufficient to invoke 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 100%, so baseline is 3. The description earns above that by explaining the relationship between parameters — cursor drives nextCursor/hasMore continuation, and convoIds switches to 'selected mode' rather than combining with pagination — which is mode semantics the schema does not state.

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 ('Export conversations for an agent') and adds scope ('all', Postgres mirror). This distinguishes it from export_conversation and list_conversations implicitly, but never names the singular export sibling explicitly.

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 useful preconditions (requires paid workspace, hasEverPaid === true, quota-billed) and explains the two operating modes (paginated vs selected via convoIds). However it never routes the agent away from list_conversations or export_conversation for single-conversation cases, so selection guidance is only implied.

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