tdarr_stats_get_streams

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

With no annotations, the description should fully disclose behavioral traits. It fails to indicate whether the tool is read-only, requires authentication, has rate limits, or what it returns. The term 'get' implies reading, but no safety or idempotency context is provided.

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?

Extremely short (two words per, including article) but under-specified. It sacrifices utility for brevity, missing key details that could fit in one more sentence.

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 complexity of the domain (many stats tools) and the lack of output schema, the description is insufficient. It doesn't explain what stream statistics are, how libraryId filters results, or what the output looks like.

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?

Only one optional parameter (libraryId) with a description that mirrors the schema. Since schema coverage is 100%, the description adds no further meaning, meeting the baseline of 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 description 'Get stream stats info' conveys a general purpose but is too vague to distinguish from sibling stats tools like tdarr_stats_get_res_hist or tdarr_stats_get_pies. It lacks specificity about what stream stats are (e.g., health, activity, errors).

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?

No guidance on when to use this tool vs the many alternative stats tools. For example, it doesn't explain if you should use this for streaming health vs tdarr_stats_get_pies for aggregated data.

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