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

No annotations are provided, so the description carries the full burden. It only states that authentication is required; it does not disclose what data is included, whether it is a costly/long operation, or any side effects (e.g., rate limits, data format). For an export tool, this leaves significant ambiguity.

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 two short sentences, front-loaded with the core action. It conveys the essential purpose without verbose filler, and every word 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?

Given that there is no output schema and the operation exports the entire account's data, the description should explain what 'data' includes, the output format, potential size or time implications, and any side effects. It mentions only auth and export, leaving the agent with insufficient context for safe/effective 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?

The tool has zero parameters)SkipSchema coverage is 100% (vacuously, since there are no params). With no parameters to explain, the baseline of 4 applies; the description adds no param info but also needs none.

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 the action: 'Export all of this account's data in one document.' It specifies the verb (export), the resource (account's data), and the deliverable (one document). This distinguishes it from siblings like get_statement or list_* tools, which are narrower or different operations.

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 gives a single precondition: 'Auth required.' It provides no guidance on when to use this tool versus alternatives, no mention of limitations or whether it is for bulk export vs. specific queries. With no sibling differentiation or exclusions, usage context is minimal.

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