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

With no annotations, the description carries the full behavioral burden. It discloses the broad data scope ('everything the shop holds') and output format ('one JSON document'), but does not state that the operation is read-only, what permissions are required, or whether large exports are synchronous or rate-limited.

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 a single, front-loaded sentence with no wasted words. It efficiently conveys scope, output shape, and purpose.

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 simple one-parameter export tool with no output schema, the description covers purpose and output format. However, it omits parameter identification details and safety/behavioral context that would matter for a privacy-sensitive data export.

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?

There is one required parameter (customer_id) with 0% schema description coverage, and the description never explains how the customer is identified. It only implies 'one customer' without adding format, source, or lookup semantics beyond the schema's UUID type.

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 states a clear outcome: exporting everything the shop holds about one customer as a single JSON document. It distinguishes itself from record-level siblings like customers_get by emphasizing comprehensive scope, though it does not explicitly name alternatives.

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 phrase 'for a privacy request' gives a clear usage context, telling the agent this is for privacy/data-access scenarios. It does not state when not to use it or name a specific alternative such as customers_get or customers_statement.

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