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

With no annotations, the description carries the full burden; it does disclose the complete data scope (conversations, sessions, leads) and the JSON format, which is useful. It says nothing about volume limits, whether the export is synchronous or a background job, authorization requirements, or rate limiting — meaningful gaps for a bulk data-egress operation.

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?

A single sentence with the purpose, scope, and format front-loaded and no filler. Every clause earns its place.

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 a one-parameter read-only export with no output schema and no annotations, the description covers what is exported, for which bot, and in what format. Missing only operational context (size, timing, permissions), which is minor for a simple tool but not trivial for a bulk export.

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 schema itself says nothing about bot_id beyond its type. The description partially compensates by indicating the export is scoped to a single bot ('held for this bot'), which ties bot_id to scope, but it never states format expectations or what happens with an invalid bot_id.

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 ('GDPR data-portability export') plus the exact scope ('every conversation, session, and lead held for this bot') and output format (JSON). An agent can distinguish it from list_conversations or list_leads, though it does not name those siblings explicitly to reinforce the bulk-vs-paged distinction.

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 'GDPR data-portability' framing implies when to use it (compliance/portability requests for a whole bot), but there is no explicit when-not guidance, no mention of alternatives like export_leads or list_conversations for narrower needs, and no prerequisites such as permission or admin scope.

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