text_to_cad

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

Discloses network call (consistent with openWorldHint), file output location, editable source, and the STARTER quality warning. Exceeds annotation alone.

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 concise sentences front-loaded with purpose, covering prerequisites, side effects, and a warning. No redundant phrases.

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?

Good context on output (files in out_dir, KCL source) and network usage, but missing explanation for two parameters and no return value details.

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 0% and description only outlines prompt and out_dir, ignoring timeout_s and output_format. Insufficient for an agent to understand all parameters.

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?

Clearly states the tool generates a STARTER CAD model from a text prompt via a specific API, which differentiates it from inspection/validation sibling tools.

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?

Explicitly mentions required environment variable (ZOO_API_KEY) and the need to verify dimensions, but does not compare to alternatives like model_build for manual modeling.

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