List subscription exports

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is largely covered. The description adds useful non-annotation context (the required subscriptions:read OAuth scope), but stops short of describing result shape, pagination semantics, or rate limits.

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?

Three short, front-loaded sentences with no filler; the core action leads and the auth constraint follows. It is efficient, though 'Reads account data' is a slightly generic restatement of the read-only annotation rather than new information.

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 paginated read-only list tool with full schema coverage, no output schema, and clear annotations, the description covers the essentials and adds the required OAuth scope. It could be stronger by clarifying where it fits relative to create_export/get_export, but nothing critical is missing for correct invocation.

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 all seven parameters (publication_id, cursor, page, limit, account, all_pages, max_items) are already richly documented in the schema. The description adds no parameter-level detail, so this sits at the baseline.

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 ('List') and resource ('subscription exports'), so the agent knows the operation. It does not, however, differentiate itself from the closely-related siblings create_export/get_export or explain what a 'subscription export' contains versus other export types.

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 only guidance is an auth prerequisite ('Reads account data. OAuth integrations require subscriptions:read.'). There is no when-to-use framing, no mention of when to prefer get_export or create_export, and no exclusions for a tool that sits among many export-adjacent siblings.

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