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

Annotations cover safety and idempotency: readOnlyHint=false, destructiveHint=false, idempotentHint=true, openWorldHint=false. The description adds useful operational constraints beyond annotations: bounded signal processing only, 8 channels maximum, and 16384 samples per channel. It does not explain failure behavior or authorization, but it meaningfully extends the annotation profile.

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 short and structured with Problem, Input, Result, and Limits sections. It is front-loaded and wastes little space, though the Input line is too vague to be useful.

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?

The tool has four required parameters, a nested request object, 0% schema description coverage, and a paid-job constraint implied by max_total_price. The description covers output evidence and signal limits, but omits required input fields, idempotency behavior, and pricing semantics, leaving key invocation details absent.

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% and there are four required parameters, including idempotency_key, max_total_price, schema_version, and a nested request object. The description says only 'Input: JSON with fixture,' which does not explain any of the actual required fields and does not compensate for the complete lack of schema descriptions.

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: generate a bounded sine or safe-formula signal fixture and return reproducibility, measurement, checksum, and validation evidence. This is clear enough to distinguish it from most sibling wave-processing tools, though it does not explicitly compare itself to alternatives such as reconstruct_bounded_capture or run_wave_job.

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 gives no when-to-use guidance, no prerequisites, and no named alternatives. It only describes the tool's problem, input, result, and limits, leaving the agent to infer when this fixture-generation tool is preferable to sibling tools.

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