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

Annotations already declare readOnlyHint=true, destructiveHint=false and closed-world, so an export being a safe read is covered. The description adds one genuine piece of new behavior: the result is CSV. It says nothing about size, cost, or the default 10k / max 50k cap that matters for a bulk export.

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?

It is short, but the first clause just echoes the name and title, so the sentence is mostly redundant rather than front-loaded with useful content. Only 'as CSV' 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?

With an output schema present, return-shape explanation is not required, but the description still leaves out how this differs from get_sequence_leads and what a bulk export entails (size, time, truncation at limit). For a tool an agent must choose over a sibling, that is a meaningful gap.

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 schema already documents id, limit (default 10000, max 50000) and workspace_id fallback behavior. The description adds no parameter meaning beyond that. Baseline 3 applies when the schema carries the parameter burden.

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?

The description restates the tool name/title almost verbatim ('Export Sequence Leads - Export sequence leads as CSV'). The only new information is the output format (CSV), which hints at how it differs from get_sequence_leads, but the tool's actual scope (which leads, what columns, per-sequence) is never stated.

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?

No when-to-use guidance is given. The sibling list contains get_sequence_leads, which is the obvious alternative, and the description does nothing to explain when an agent should export versus read leads via that tool. Nothing about prerequisites (sequence must exist, workspace scoping) is mentioned.

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