get_stream_stats

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

With no annotations at all, the description carries the full burden and discloses very little. 'Real-time' hints that the data is live and ephemeral, but there is no mention of whether an active stream is required, whether results are cumulative or per-window, whether the call is read-only, or whether it is rate-limited.

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 tight sentence with no filler, and the key qualifier ('real-time') is placed early. It is efficient but so short that it omits rather than organizes information.

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?

For a zero-param tool with no output schema and no annotations, the description is the only source of information about what comes back, and it never names a single metric or return shape. An agent cannot tell whether it gets latency, throughput, error rates, or connection counts.

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 tool takes zero parameters, so the baseline is 4 and there is nothing the description could add about argument meaning. The only residual question is what scope (global vs. per-stream) the parameterless call defaults to, which is a minor gap.

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?

States a specific verb ('Get') and resource ('real-time streaming statistics and performance metrics'), so the agent knows this is a metrics-retrieval tool rather than an analysis one. It does not, however, differentiate itself from siblings like stream_check or stream_batch, which also operate on the streaming path, so the boundary between 'stats' and 'check' is left to inference.

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?

There is no explicit guidance on when to call this versus stream_check, stream_batch, or analyze_corpus. The agent must guess whether stats are needed before, during, or after a stream, and whether any prerequisite stream must exist.

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