Quady3D create job

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

Annotations already declare idempotentHint and openWorldHint, but the description adds the material facts those hints cannot convey: the call 'reserves credits' (a financial side effect) and 'Returns immediately', so the agent knows this is async. The retry-safety guidance operationalizes the idempotency hint rather than repeating it.

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?

Front-loaded with the action and its prerequisites, then retry semantics, then the async/credit warning. Dense but every clause carries operational meaning; no filler.

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?

No output schema exists, and the description never says what the call returns (e.g. a job identifier) or how to correlate the response with quady3d_get_job beyond 'query the same job'. Credit reservation and interrupt/reconnect handling are covered, but the return contract is left implicit for a mutation that spends money.

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 coverage is 33% – only client_action_id is documented inline, so the description must compensate. It conveys that quote_id refers to a 'saved quote' and that max_credits is a spend ceiling ('within max_credits'), but gives no format, source tool, or behavior when the quote expires or the cap is exceeded.

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 and resource: 'Start a user-authorized generation ... using a saved quote and a ready project directory.' That clearly separates it from quady3d_quote (pricing) and quady3d_get_job (polling). The only friction is the name says 'job' while the description says 'generation', which an agent must reconcile.

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?

Gives a concrete reuse rule for interruptions ('Reuse the exact client_action_id, quote and limit... including when the directory needs reconnecting') and routes follow-up to 'query the same job'. It stops short of an explicit when-not-to-use or naming quady3d_get_job, but the context is strong.

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