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

Although annotations already mark this as read-only, idempotent, and non-destructive, the description adds important behavior: background CSV generation, a wait of about a minute, possible retry request, and a sign-in-free link that expires after 24 hours.

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?

The description is front-loaded with the primary outcome and uses each sentence to add distinct value: CSV contents, wait behavior, link expiry, and the filtered alternative. There is no redundant restatement of the tool name or annotations.

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 still explains the returned artifact: a CSV download link, row count, included columns, and link expiry. It also covers the background build and retry behavior, leaving no important operational gap for this zero-parameter export tool.

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?

The tool has zero parameters, so there is no parameter meaning to clarify. The baseline for a zero-parameter tool is 4, and the description does not need to compensate for missing input metadata.

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 states a specific action and resource: exports the full subscriber list as a CSV download link with row count. It also distinguishes this from filtered list retrieval by naming list_subscribers as the alternative.

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?

It explicitly says to use list_subscribers for filtered pages, which defines when this tool is and is not appropriate. It also explains the wait behavior and what to do if the export is not ready.

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