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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description's only added behavioral context is the 'authorized' access constraint and the scope (Wave/Studio managed-simulator jobs); it says nothing about job states, error behavior, or what 'status' encompasses.

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 front-loaded sentence with no filler, which is appropriate for a simple read tool. It is arguably too terse for the ambiguity it leaves, but nothing in it is wasted.

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-value explanation is not needed, and annotations cover the safety contract. The remaining gap is disambiguation from the cluster of sibling retrieval tools, which the description does not address for an agent selecting among ~35 related tools.

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% and the anyOf variants already encode the job_id/product/schema_version contract, so the schema does the heavy lifting. The description adds no parameter detail (e.g., that 'Studio' maps to the 'quantum' product enum value), leaving the naming mismatch unexplained.

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 clear verb ('Read') and a specific resource ('one authorized Wave or Studio managed-simulator job'), so an agent knows it retrieves a single job. However, it never states that what comes back is *status* (the meaning the tool name carries) and does not distinguish itself from siblings like get_wave_job_result, get_wave_job_artifact, or get_wave_receipt.

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 call this versus the other job-retrieval siblings (get_wave_job_result, get_wave_job_artifact, get_wave_receipt), and no stated preconditions beyond the word 'authorized'. The agent is left to infer the selection criteria entirely.

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