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

Beyond the readOnlyHint/destructiveHint annotations, the description discloses the 200-row cap, that the response includes a header row plus a truncation notice, that unrevealed stores are silently skipped, and that a paid plan is required. These are exactly the constraints an agent needs before calling, and none are available from structured fields.

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?

Four short sentences, front-loaded with purpose and format, then constraints, then the alternative. No filler, though the trailing "Paid plans only" could sit closer to the export statement for faster scanning.

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 read-only export tool with a fully described nested schema and no output schema, the description covers output format, row limit, truncation signaling, scope exclusion and plan gating. An agent has everything needed to decide and invoke 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?

Schema description coverage is 100% and the nested selection object (ids vs tab with filters/deselected) is fully documented in the schema itself. The description only alludes to "narrow the selection" without adding format or precedence detail beyond what the schema already provides, so the baseline of 3 applies.

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?

"Export revealed stores as CSV text" gives a specific verb (export), a scoped resource (revealed stores) and an output format (CSV text). It is immediately distinguishable from siblings such as searchStores or revealStores without opening the schema.

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 states the exclusion rule (unrevealed stores are skipped) and routes large exports elsewhere: narrow the selection or download from the dashboard. It does not name sibling tools like searchStores for obtaining ids, but the usage context is clear and includes a genuine when-not path.

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