statsfm_recent_streams

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

No annotations are present and the description gives no behavioral details. It does not state whether the tool is read-only, whether it requires authentication, whether it has rate limits, or what side effects might occur.

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 description is very short and front-loaded, but it is under-specified rather than efficiently complete. It reads more like a label than a functional description, leaving out the verb and key context.

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?

There is no output schema and the description does not explain what the returned streams look like, how many are returned by default, or how response_format changes the output. The schema's enum description helps, but the overall context is incomplete for an agent to confidently select and call the tool.

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 schema covers all six parameters with descriptions, so the baseline is met. However, the tool description itself adds no additional meaning beyond the schema fields such as the exact timestamp format, default ordering, or interaction between after/before and limit/max_results.

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 identifies the resource (stats.fm recent streams) but uses a noun phrase instead of an explicit verb like 'get' or 'list'. It is somewhat distinguishable from the many statsfm_* siblings by the 'recent_streams' name, but does not clearly state the action or 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?

There is no guidance on when to use this tool versus alternatives such as get_recently_played, statsfm_streams_stats, or statsfm_now_playing. No conditions, exclusions, or example scenarios are provided.

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