tracearr_get_streams

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

The description adds behavioral detail beyond the readOnlyHint annotation by explaining the effect of summary=true (returns only summary stats, omits data array) and that streams carry canonical media identity. This gives useful context about output shape and parameter behavior without contradicting the annotation.

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 short sentences, front-loaded with the core purpose, and no redundant or filler content. Every sentence adds information: purpose, output characteristics, and parameter behavior.

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?

Given the output schema exists to describe return values, the description adequately covers the main use case and summary option. The only apparent gap is the server_id parameter's role, which could affect completeness for users wanting to filter by server.

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 description explains the summary parameter's effect (returns summary stats, omits data array), but does not mention server_id at all, leaving its meaning or filtering behavior unclear. Since the schema descriptions are absent, the description should compensate more fully for both parameters.

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 clearly states the tool returns 'Currently active playback sessions across all servers,' which is a specific verb+resource+scope. It distinguishes from sibling tools like tracearr_get_history or tracearr_get_media by focusing on live streams rather than historical or static media data.

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?

The context is clear: this is for active playback sessions across all servers. However, it does not explicitly mention when not to use it or name alternative tools, so it misses the explicit exclusion criteria that would earn a 5.

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