Quady3D quote

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

Annotations already declare readOnlyHint/idempotent/non-destructive, and the description adds genuinely non-obvious behavior: no charge is incurred, connection-scoped input is persisted for a later create_job call, and the quote has a 5-minute TTL. There is mild tension between 'readOnlyHint: true' and the stated persistence of input state, but it reads as a non-mutating quote record rather than a real contradiction.

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?

Three short sentences, front-loaded with the core action, and every clause adds distinct information (cost, downstream use, expiry). No filler or restatement of the title.

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?

With no output schema, the description should say what a quote returns (a price, a quote identifier, expiry token) and how create_job consumes it; it only says the input is saved for the same connection. The cost/expiry lifecycle is covered, but the return shape and handoff mechanism are left implicit.

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 reported at 100%, so the schema carries the parameter burden and baseline 3 applies. The description adds no meaning about `model`, the free-form `parameters` passthrough, or the `upl_...` upload_id requirement for the image-to-3d branch, all of which an agent must infer from the schema alone.

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?

Names a specific verb and resource (quote a text or single-image 3D generation) and explicitly contrasts with the charging path by saying 'without charging' and pointing at create_job. An agent can distinguish it from quady3d_create_job, though it never states the two operations map to the text-to-3d and image-to-3d branches of the schema.

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?

'Saves this connection's input for create_job' plus the five-minute expiry clearly signals the intended workflow: quote first, then create. It does not state any explicit when-not or what happens if the quote is not consumed, so it falls short of full routing guidance.

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