scan_output

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

Discloses what is scanned (PII, secrets) and return format. No annotations, but description covers main behavioral aspects. Minor omission: no mention of idempotency or side effects.

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?

Concise: a one-sentence purpose, usage instruction, and structured Args block. No wasted words; every sentence adds value.

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?

Despite no output schema, the description covers return values in detail. Tool is simple and well-explained; sibling tools are different, so no confusion.

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 only parameter 'text' has no schema description (0% coverage). The description's Args section provides detailed explanation of what text should contain, adding significant value.

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 explicitly states the tool scans outgoing text for PII and secrets, using specific verbs and resources. It differentiates from sibling 'scan_input' by specifying outgoing vs incoming.

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?

Provides clear context: use on agent-generated responses before sending, posting, or logging. Lacks explicit 'when not to use' but the context is sufficient.

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