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

Annotations already declare the safety profile (not read-only, idempotent, not destructive, closed-world). The description adds useful operational limits (bounded signal processing, 8 channels, 4096 samples/channel) and states the result form, but is silent on cost/authorization even though the schema fixes max_total_price, so an agent gets no hint that this is a priced job submission.

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 labeling is well structured and front-loaded, but the Input sentence is visibly truncated ('maximum....'), which costs clarity and wastes the section that most needs completeness.

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 described, but the input is an opaque nested 'request' object with 0% schema coverage and four required fields, two of which (idempotency_key, max_total_price) are never addressed. For a job-submission tool with fixed pricing and a generic request envelope, the definition is materially incomplete.

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 coverage is 0% and the description lists request-internal fields (observation, reference, assumed transfer, maximum rmse) but truncates mid-list ('maximum....'). The three other required top-level parameters (schema_version, idempotency_key, max_total_price) receive no explanation at all, so the description fails to compensate for the coverage 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?

States a specific verb+resource: reconstruct a 'bounded capture' under a transfer assumption and verify against reference rules. 'Bounded' plus the limits line distinguishes it somewhat from the vaguer sibling wave_reconstruct_time_domain_signal_v1, though it never names that sibling or states the boundary explicitly.

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?

No when-to-use or when-not-to-use guidance. There is no mention of how this differs from siblings like wave_reconstruct_time_domain_signal_v1 or wave_validate_reconstruction_quality_v1, leaving selection to inference from the word 'bounded'.

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