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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds real context with 'approved public' (only approved, publicly visible capabilities are returned) and 'full' (complete descriptor rather than a summary), but says nothing about auth, error behavior, or not-found handling.

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 compact sentence with the verb and resource front-loaded and no filler. It is efficient, though arguably too terse for a tool whose schema exposes four request variants.

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 description is not required. Against a four-variant anyOf request schema and a large sibling set, however, the description omits variant selection guidance (which schema_version/product to send) and any routing to list_capabilities, leaving real gaps.

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?

Per the context there are 0 top-level parameters and schema description coverage is 100%, which normally sets a baseline of 4. The description adds no meaning of its own and does not explain the product/capability_id/schema_version request variants (v1-v4) expressed in the anyOf; its 'Wave' wording could mislead about the product field, so it sits below the baseline.

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 ('Return') and resource ('one full approved public Wave capability descriptor'), and the singular 'one' implicitly contrasts with the sibling list_capabilities. However it never names that sibling explicitly, and narrowing to 'Wave' is slightly at odds with the schema's multi-product (wave/quantum/robotics) request variants.

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 mention of list_capabilities as the alternative for enumerating capabilities, and no prerequisites or conditions. The agent must infer that this is the single-item lookup variant purely from the word 'one'.

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