wave_list_blocks

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

With no annotations, the description carries the behavioral burden and does disclose the required Seashell Helper block prerequisite. It implies a safe read via 'List' but does not cover pagination, error behavior, or what happens if the helper is unavailable, leaving meaningful gaps.

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 two sentences, front-loads the main action, and contains no waste. The prerequisite is placed after the core purpose without obscuring it.

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 filtered list tool, the description covers the core action, filters, and a key prerequisite. But with no annotations and no output schema, it omits expected return content and behavioral details such as pagination or helper-missing errors.

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?

Schema description coverage is 100%, so the input schema already documents all three filter parameters. The description mentions the same filter categories, matching the schema, but adds no extra parameter semantics beyond that.

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 states a specific verb and resource, 'List blocks in Wave Terminal,' and adds optional filters. It is clear enough to distinguish from block mutation tools and workspace listing tools, though it does not explicitly name sibling alternatives.

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?

It explains optional filtering by workspace, tab, or view type and notes the Seashell Helper dependency, which gives useful usage context. However, it does not say when to choose this tool over related listing or environment tools, and it gives no explicit exclusions.

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