gdpr_export_customer_data

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

No annotations are provided, so the description must convey behavioral details. It states 'exporta todos los datos almacenados' but does not explain the return format (e.g., file, link), whether the operation is asynchronous, or any side effects. This lack of behavioral disclosure is a significant gap.

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 sentence that conveys purpose effectively. However, the trailing '[query]' appears to be a formatting artifact and could cause confusion. Otherwise, it is concise and front-loaded.

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 purpose (GDPR data export) and the absence of an output schema, the description should indicate what the output is (e.g., a downloadable file, a link). It fails to describe the outcome, leaving the agent uncertain about how to retrieve the exported data.

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 input schema has one required parameter 'phone' with a description. Since schema coverage is 100% and the description adds no additional meaning beyond what the schema provides, the baseline score 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?

The description clearly states the verb 'Exporta' (exports) and resource 'datos del cliente' (customer data), and specifies it is for GDPR compliance (Art. 15 right of access). This distinguishes it from the sibling tool 'gdpr_delete_customer_data' which performs deletion.

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 implies usage for GDPR access requests by citing Article 15. However, it does not explicitly state when not to use it or mention alternative tools like 'gdpr_delete_customer_data'. The context is clear but lacks explicit exclusions.

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