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

With no annotations, the description carries the full burden and does disclose key traits: RESTRICTED drives blocked=true, the tool is non-enforcing, and the result includes retention info and a tamper-evident receipt. It omits whether the sample itself is retained/logged (implied by 'retention info') and any auth or rate-limit requirements.

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?

Three tight sentences, front-loaded with the core action, followed by the exclusivity caveat and return summary. No filler or repetition of the tool name.

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?

An output schema exists, yet the description still summarizes the returns, which is mildly redundant but helpful. Combined with the classification semantics and enforcement boundary, an agent has enough to decide whether to call it; the main gap is undocumented parameter formats.

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 description coverage is 0% for all three required parameters, so the description must compensate and largely does not. It implies data_sample is what gets scanned but says nothing about the format or meaning of 'provider' and 'destination' (e.g., is provider an email/cloud vendor, is destination a URL?).

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 specific verb and resource ('scans a data sample for sensitivity markers and classifies') and names the exact output taxonomy (NO_MARKERS_FOUND / INTERNAL / CONFIDENTIAL / RESTRICTED). This is distinct from siblings like gate_decision or verify_receipt, which handle enforcement and receipts respectively.

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?

It clearly bounds the tool's role with two strong exclusions: 'this tool cannot block anything itself' and 'NO_MARKERS_FOUND is not clearance to send.' However, it never names the alternative tool (e.g., gate_decision) that does perform blocking, so the agent must infer the routing itself.

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