gdpr_scan_project

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

With no annotations, the description carries the behavioral burden. It discloses return value composition ('flagged files with data categories and applicable GDPR articles') and implies a read-only scan ('Find every file'). It also mentions '5 seconds' and 'free' as operational traits. The 'no arguments' claim is slightly offset by the optional project_path parameter, but not harmful.

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 utility sentence 'GDPR fines reach 20M EUR or 4% turnover' is irrelevant to selecting or invoking the tool and wastes a slot. The useful information (function, speed, cost, output) is front-loaded, but the fine scare line is extraneous.

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?

The tool is simple (one optional parameter, no output schema) and the description sufficiently explains what it does, what it scans for, and what it returns. It also provides a pointer to an alternative for combined requirements, making it complete for practical use.

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 100%, with a single optional parameter already well-described ('Leave empty or pass '.' to scan the current directory'). The tool description adds no parameter-specific meaning beyond saying 'no arguments', which actually understates the optional project_path parameter. Thus baseline 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 a specific verb and resource: 'Find every file in your project that touches personal data.' It enumerates what is detected (PII, cookies, tracking pixels, analytics SDKs, consent flows) and distinguishes itself from generic scan_project by focusing on GDPR. It also points to combined_compliance_report for a different scope.

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 provides context on when to use this tool ('no arguments, 5 seconds, free') and explicitly directs users to combine with EU AI Act via combined_compliance_report(). However, it does not articulate exclusions or contrast with sibling tools like gdpr_check_compliance or scan_project.

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