subscriber_bulk_export

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

No annotations exist, so the description carries the full burden. It discloses the default for include_ha1 and warns about credential material, and specifies the limit default and maximum. This adds behavioral context beyond the schema. However, it doesn't mention idempotency, rate limits, or side effects (though it's a read 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?

The description is concise: a one-line summary followed by a structured parameters section. Each parameter is explained in one line with relevant defaults and warnings. No redundant 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?

Given the tool's simplicity (3 parameters, an output schema exists), the description covers all essential aspects: input parameters, their defaults, a security warning, and the output format (CSV text). It is complete enough for an agent to use 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?

With 0% schema description coverage, the description compensates fully by explaining each parameter: domain (optional filter), include_ha1 (default false, security warning), limit (default and max 5000). This adds significant meaning beyond the plain schema.

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 clearly states 'Dump subscribers as CSV text,' specifying both the action (dump) and the output format (CSV). This distinguishes it from sibling tools like subscriber_list (likely JSON) and subscriber_bulk_import (import).

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 description provides some context (optional domain filter, security warning for include_ha1, limit cap) but does not explicitly explain when to use this tool versus alternatives like subscriber_list or subscriber_get. The usage is implied but not contrasted.

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