STEP/IGES CAD to URDF

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

Discloses that solids are welded with fixed joints and that the first call loads a 7.6 MB OCCT kernel, adding valuable context beyond annotations (readOnlyHint, idempotentHint, destructiveHint). No contradictions.

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?

Two-sentence description is highly concise, front-loads the core purpose, and every sentence adds value without extraneous text.

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 input and computation but omits description of the tool's output or return value. No output schema is present, so the description should clarify how results are returned.

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 description coverage is only 50%; description does not add parameter-specific information. Does not compensate for missing schema descriptions on filename and density.

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?

Explicitly states conversion from STEP/IGES CAD to URDF, with specific details about computing mass properties and joining solids. Clearly distinguishes from sibling conversion tools targeting other formats.

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 guidance on when to use this tool versus alternatives like sdf_to_urdf or xacro_to_urdf. Agent must infer based solely on input format.

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