Quady3D list models

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

Annotations already establish that this is a read-only, idempotent, non-destructive, open-world operation. The description adds useful context beyond the annotations: it says there is no generation charge and warns that older APIs may omit parameter definitions, so defaults should be used rather than guessed.

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 description is compact and front-loaded with the core purpose. Each sentence adds a distinct piece of value: return contents, model selection guidance, omission caveat, and cost clarification.

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?

The description compensates for the lack of an output schema by explaining what model information is returned, and it covers key caveats. However, it omits any explanation of the only input parameter, leaving a meaningful gap for a tool whose schema description coverage is 0%.

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?

The sole parameter is an optional 'operation' enum with values 'text-to-3d' and 'image-to-3d', but the schema provides 0% description coverage and the tool description never mentions this parameter. It does not explain whether omitting it lists all models or what each enum value filters, leaving the schema's enum values to speak for themselves.

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 description states a specific verb and resource: it lists model availability, input limits, and parameter schemas. The phrase 'before quoting' hints at its relationship to quady3d_quote, but it does not explicitly name or distinguish other sibling tools such as create_job or get_job.

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 clear usage context: select an explicit available model and respect its parameter definitions before quoting. It also advises using defaults when older APIs omit definitions. However, it does not explicitly state when not to use this tool or name a direct alternative.

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