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

Annotations already declare write, idempotent, non-destructive and closed-world, so the bar is lower, yet the description still adds real value: the idempotency mechanism (a *stable* clientRequestId reused across retries) and an approval gate. The recovery reference is opaque and points at "oauth_v2" rather than the visible get_media_operation sibling, which muddies rather than clarifies the retry story.

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?

Two sentences, no filler, with the core action and the idempotency requirement front-loaded. The second sentence is telegraphic to the point that "query oauth_v2 operation recovery" reads as jargon an agent may not be able to act on.

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?

For a 2-parameter write tool with no output schema, the description covers prerequisites and the uncertain-response case but never says what comes back (a task or operation identifier) or how to poll it, which is the key missing piece for a submission tool.

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%, so the description must carry parameter meaning. It does explain that clientRequestId must be stable (an idempotency key) and that quoteId refers to a verified quote, but it says nothing about the 8–64 character constraint or the expected ID format, leaving the constraints entirely to the bare schema.

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?

"Confirm a verified quote" states a specific verb and resource, and the clientRequestId framing makes it clear this is the submission step that follows quoting. It is distinguishable from quote_media_task and the get_/list_ siblings, though it never states outright that it creates a media processing task.

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?

"Obtain user approval first" gives one concrete precondition and the recovery path covers the failure case. However, it never names the prerequisite sibling (quote_media_task) that produces quoteId, and gives no when-not guidance against submit_subtitle_task or the watermark task tools.

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