list_streams

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

With no annotations provided, the description carries the burden of behavioral disclosure. The verb 'list' implies a read-only, non-destructive operation, but the description does not explicitly confirm safety, permissions, or output format. It provides minimal behavioral context beyond the obvious.

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, focused sentence that immediately states the purpose with no filler or redundant detail. The structure is clean and front-loaded with the verb.

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 simple listing tool with one optional parameter, the description is adequate. It implies a list output and the schema covers filtering. However, it does not explicitly mention all stream types supported by the enum, and there is no output schema, but the tool's simplicity makes this a minor gap.

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 input schema fully documents the single parameter stream_type with an enum and description, so the description adds no additional semantic value. The parenthetical in the description lists a subset of enum values, but it does not explain parameter behavior or format beyond the schema.

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 uses a specific verb ('list') and a clear resource ('available streams'), with a parenthetical enumerating common stream types. This directly states what the tool does and distinguishes it from siblings like search_logs or aggregate_logs, which operate on stream data rather than enumerating streams.

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. No alternatives, prerequisites, or exclusions are mentioned. The sibling tools suggest different use cases, but the description does not connect to them or provide any context for selection.

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