observe_chat

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

Despite annotations declaring destructiveHint=true and idempotentHint=false, the description adds meaningful behavioral detail: the scan-then-gate-then-record-then-run sequence, the block_threshold gating logic, and the WRITE/risk=medium tag. This goes beyond what annotations provide.

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 [WRITE][risk=medium] prefix front-loads the mutation and risk profile efficiently. The Args block is structured and readable, though slightly verbose in listing trivial parameters.

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?

No output schema exists, so the description should explain what is returned (the model response? a policy decision?). It doesn't. For a mutation tool with pipeline behavior, the absence of return-value context is a notable gap.

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%, so the description must compensate. It documents all 6 parameters reasonably — model, messages, agent/user, block_threshold, target — but lacks detail on format syntax (e.g., valid risk bands for block_threshold, config target format). Adequate but incomplete.

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 uses a specific compound verb sequence: 'Scan + policy-gate a chat exchange, record it, then run if allowed.' This clearly states what the tool does. It is distinguishable from guarded_generate and scan_prompt, though it doesn't explicitly name those siblings to differentiate.

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?

Usage is implied by the pipeline description but no explicit when-to-use vs alternatives is given. The relationship to guarded_generate and scan_prompt is unclear — an agent cannot tell which tool to pick for a given task.

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