stream_batch

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

No annotations are provided, so the description bears the full disclosure burden. Beyond 'real-time' and 'high-throughput' it says nothing about ordering guarantees, partial-failure behavior within a batch, rate limits, or what happens if some messages fail - all material for a streaming batch endpoint.

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?

A single short sentence with no filler and the high-level mode stated up front. It is tight, but its brevity is partly under-specification rather than economy.

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?

Five parameters, a nested message array, no annotations, and no output schema - yet the description never says what the result looks like or what the messages are checked against (the languages enum implies matching against something undefined). For a batch/streaming mutation-shaped tool this leaves too much unresolved.

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 100%, including defaults for caseSensitive, detectLeetspeak, and normalizeUnicode and the min/max item bounds, so the schema already documents every parameter. The description adds no semantics beyond it, which puts this at the baseline 3.

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 verb is 'process', which is generic and never states what processing actually is - profanity checking, content validation, PII scanning, or something else. Given siblings named stream_check, batch_check, and check_profanity, an agent cannot tell what stream_batch produces that those do not; only 'multiple messages' and 'batch mode' hint at 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?

'for high-throughput scenarios' is the only usage hint, and it describes a performance profile rather than a decision rule. It never names stream_check or batch_check as alternatives, so there is no guidance on when this tool should be chosen over them.

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