get_safety_report

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

No annotations provided, so description carries full burden. It explains what the tool returns (regulation triggered, problematic fields, redaction strategy, compliant reformulation) and the consequences of not using it (unremediated violation, no audit trail).

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?

Several sentences but each adds value. Front-loaded with purpose, then usage guidelines, then outcomes. Could be slightly more concise, but no superfluous content.

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 6 params (1 required), 100% schema coverage, and output schema exists, description fully covers when to use, what it returns, and consequences. No missing guidance.

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%, baseline 3. Description adds value by explaining workflow linking modes (REPORT, BATCH, AUDIT) to prior tool usage, though schema already documents enums. Extra context like 'immediately after validate_data_safety' goes beyond 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 clearly states the tool retrieves a 'detailed compliance report and remediation strategy' for a 'flagged payload'. It uses a specific verb ('Retrieves') and resource, and distinguishes from siblings by positioning it after 'validate_data_safety' returns non-SAFE verdicts.

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?

Explicitly states when to call: after 'validate_data_safety' returns 'REDACT_BEFORE_PASSING, DO_NOT_STORE, or ESCALATE'. Warns against proceeding without it, providing clear context for use.

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