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

Annotations only cover readOnlyHint=false and openWorldHint=true, so the description carries most of the burden and delivers real value: asynchronous execution, idempotency-key retry semantics, allowlist-gated access, and unbilled preview status. It does not disclose the return shape or polling requirement, which keeps it from a 5.

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 three clauses are compact and the core action is front-loaded, which is good. The trailing fragment "discovery reports blueprint maintenance" is cryptic and reads as an unrelated note, costing a point on structure and clarity.

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?

This is an asynchronous mutation with no output schema and a nested, wholly undocumented parameters object. The description omits the critical follow-up workflow (what identifier comes back, that the agent should poll get_job) and the blueprint allowlist specifics, leaving the agent under-equipped to complete the task beyond the initial call.

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% across 5 parameters, so the description must compensate and largely fails: it mentions only the URL and idempotency key, and gestures at blueprints via "allowlisted." It says nothing about the blueprint_id enum values, the nested `parameters` object (a nested object with no documentation anywhere), or `blueprint_version`.

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 first sentence gives a specific verb and resource ("Submit one URL asynchronously"), which is clearly distinct from read-side siblings like get_job, get_results, and search_products. It stops short of explicitly differentiating itself from run_tool, the closest sibling, so it lands at 4 rather than 5.

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?

It gives one concrete operational rule ("Keep the same idempotency key on retries") and flags the access/price context ("allowlisted, unbilled ... preview"), which does imply when this tool is usable. However, it never states when to choose submit_job over run_tool, nor what to do after submitting (poll with get_job), so usage is only partially covered.

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