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

Annotations already declare idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is partly covered. The description adds the semantics-preservation promise, which is real behavioural context, but says nothing about the paid nature of the call (max_total_price, payment_rail), what happens on failure, or whether a job is created. For a non-readOnly tool with 0% schema coverage, that is thin.

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?

It is a single front-loaded sentence with no filler, which is structurally clean. However, its brevity is a symptom of under-specification rather than distillation: it restates the title verbatim and carries no additional operational information.

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 side is a nested, multi-required-parameter paid request with zero schema descriptions and the description compensates for none of it. Given the complexity signals (nested objects, payment fields, enum plus idempotency requirement), the definition is not complete enough to call the tool confidently.

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% for four parameters, three of them required, including non-obvious ones like idempotency_key, max_total_price and payment_rail. The description only gestures at the target framework and even names a value (OpenQASM 3) that is not in the enum, leaving input format, coupling map, basis gates and pricing entirely 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?

Tautological: description restates name/title.

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 guidance, no mention of alternatives, and no statement of prerequisites or cost implications despite the tool requiring max_total_price and an idempotency_key. The only usage signal is the phrase 'without silently changing its supported semantics', which implies a fidelity guarantee but never says when that matters versus a plain transpile.

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