Export bounded private metadata

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so safety is partly covered. The description adds substantial context beyond them: exclusive 0600 file creation, page/item/5MiB budgets, page/offset continuation, and explicit non-guarantees (no atomic backup, no link following, no binary downloads).

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?

Two sentences with no filler, but the density of hyphenated jargon ('native page/size/results', 'exclusive0600', 'page/item/5MiB') hurts readability and front-loading. It is compact yet not easily skimmable.

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 an 8-parameter, nested-object write tool with no output schema, the description covers file permissions, size caps and non-guarantees, which is meaningful. It still omits the file's format/structure, failure behavior, and permission requirements, so it is adequate but not complete.

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 coverage is only 38%, so the description needs to compensate. It does explain the page/item budget and offset-continuation concepts, which map to max_pages, max_items and start_offset, but account, confirm, arguments and operation are left entirely to the 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 names the verb (export) and the resource (bounded private metadata written to a new exclusive 0600 file), which is enough to distinguish it from the many list_*/get_* siblings that only read data. The phrasing 'native page/size/results export' is jargon-heavy and takes effort to parse, but the core action is identifiable.

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?

There is no explicit statement of when to use this over the sibling list_products/list_orders/list_promotions calls it wraps, nor any when-not guidance. The word 'Confirmed' hints that a confirmation step is expected, but the description never says so directly or names an alternative.

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