list_streams

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

Despite no annotations, the description clearly explains the sorting order (newest first) and pagination mechanism. It also describes the effect of each parameter on the returned streams, adding significant value beyond the empty schema descriptions.

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 concise and well-structured, with a clear main sentence followed by bullet points explaining each parameter. Every line adds value.

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 (and is not shown), the description appropriately focuses on input and behavior. It covers most aspects, though missing page_size and lack of error handling are minor gaps.

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 4 of the 5 parameters (port, starting_from, favorites, pattern_id) but omits page_size. With 0% schema coverage, it should cover all parameters; the omission leaves a 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?

The description clearly states 'List streams (newest first)', using a specific verb and resource. It also distinguishes itself from siblings by focusing on listing multiple streams with filtering options.

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 description provides explicit guidance for each parameter: port restricts to a service, starting_from is for pagination, favorites filters, pattern_id matches patterns. It also suggests combining with create_pattern and pattern_lookback for retroactive search.

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