export

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

No annotations provided, so description carries full burden. It discloses error behavior on format mixing, labeling in STEP exports, and output sanity checks (volume/bbox). Lacks mention of authorization or side effects.

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?

Description is lengthy but informative. Could be more structured (e.g., bullet points) but each sentence adds value. Slightly verbose for a 3-parameter tool.

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?

Covers return values (volume/bbox/face count) without relying on output schema. Addresses both 2D and 3D cases. Lacks info on file naming conventions or overwrite behavior, but sufficient for basic use.

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 has 0% parameter description coverage, but the description explains all three parameters: filename (required), format (default 'step', list support), and object_name (default current, '*' exports all). Adds critical context beyond schema titles.

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 clearly states 'Export model' and details format options (step, stl, dxf, svg) with 2D/3D differentiation. It distinguishes from siblings by being the only export tool among analysis, import, and rendering 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?

Provides clear guidance on when to use each format (dxf for handoff, svg for docs) and warns against mixing 2D/3D formats. Lacks explicit when-not-to-use but covers key use cases.

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