gdpr_generate_deletion

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only says 'Generate right-to-erasure implementation.' It does not disclose whether files are written or modified, whether the API key is required for an external service, or what side effects occur. For a code-generation tool, this is a significant transparency 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 concise sentence with no redundant filler. The key concept, right-to-erasure, is front-loaded and clarified with the parenthetical 'data deletion.' It is terse, though the terseness sacrifices useful detail.

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 lack of output schema and annotations, the description is insufficient context for a 3-parameter tool. It doesn't explain what 'implementation' means as an output, how language and directory are used, what api_key is for, or how this relates to the broader GDPR workflow. An agent would have to infer critical invocation details.

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 schema describes language and directory, but the description adds no parameter-level meaning. The optional api_key parameter is undocumented in both the schema and description, leaving its purpose unclear. With 67% schema coverage and no compensating description, the agent gets incomplete guidance for invoking the tool correctly.

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 identifies the tool's purpose: generating a GDPR right-to-erasure (data deletion) implementation. It uses a specific verb and resource, and is distinguishable from sibling tools like gdpr_generate_consent and gdpr_scan_pii. However, 'implementation' is somewhat broad and doesn't specify what artifact is produced.

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 guidance on when to use this tool versus alternatives such as gdpr_generate_consent or gdpr_compliance_report. No prerequisites, workflows, or exclusions are mentioned. The usage context is only implied by the tool name and brief description.

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