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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, openWorldHint=false, so safety and idempotency are covered. The description adds genuinely useful behavioral bounds beyond those annotations: 'Bounded signal processing only; 2 channels; 1024 samples/channel'. It does not mention the implied paid cost (max_total_price const) but the added limits are substantive and consistent with the annotations.

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 Problem / Input / Result / Limits framing is front-loaded and each clause carries information (verb, inputs, outputs, constraints) with no filler. The 'wave_verify_wave_pipeline' naming redundancy aside, the prose itself is tight and well organized.

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?

An output schema exists, so return values need not be explained, and the hard limits are supplied. However, given the freeform, undescribed `request` object and three undescribed required envelope params, the description is not complete enough for an agent to confidently construct a valid call, and it offers no routing guidance among the numerous pipeline siblings.

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 0%, so the description carries the full burden. It enumerates request contents (sample rate hz, channels, operators, assertions) but omits the three other required envelope parameters (schema_version, idempotency_key, max_total_price), leaving the agent without meaning for idempotency_key or the pricing const. Partial compensation only.

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 gives a specific verb pair (execute and verify) plus a concrete resource (bounded Wave IR pipeline), and states what it produces (execution result and shape/round-trip checks). It is clear on its own, but it never distinguishes itself from closely named siblings like wave_compare_pipeline_responses_v1 or wave_optimize_processing_pipeline_v1, so the agent has no explicit basis for picking it over them.

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 when-to-use statement, no prerequisites, and no alternatives named among the many wave_* siblings. The phrase 'optional round-trip assertions' hints at a verification use case but does not tell the agent when this tool is the right choice versus compare/optimize/validate variants.

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