export_step

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

No annotations, so the description carries the full burden. 'Real analytic B-rep, always' usefully signals output fidelity (no tessellation), but nothing is said about where the file is written, whether an existing file is overwritten, permissions, or failure modes for unsupported geometry.

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?

A single front-loaded sentence with the key claim (analytic B-rep) up front and zero padding. Its brevity is close to the limit of usefulness but not wasteful.

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?

An export tool with no annotations, no output schema, and half-documented parameters needs to say where the file lands and what is returned. The description supplies only the file-format fidelity claim, leaving the operational essentials unstated.

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 50%: design_id has no description at all, and output_dir only carries 'Default: ""'. The description adds nothing — it doesn't explain what design_id refers to or what an empty output_dir means (working directory? server-side path? default export folder?).

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: export a design as a STEP file. The 'real analytic B-rep, always' clause distinguishes it from mesh export siblings such as export_model_3mf, though it never names an alternative explicitly.

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?

No indication of when to use this versus check_step_support, step_file_info, import_step_file, or export_model_3mf, and no prerequisites (e.g. whether STEP support must be verified first). The agent must infer the routing from the tool name alone.

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