rhino_export_dxf

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

Annotations already indicate readOnlyHint=false, so the write nature is known. The description adds the 'bridge required' prerequisite, which is a useful behavioral constraint. However, no details on side effects, file overwriting, or output behavior are provided.

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 extremely short (one sentence), but it omits crucial information like parameter details and usage context. While concise, it sacrifices completeness, so it is not well-structured for an agent.

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?

Given the large number of sibling export tools and the presence of three parameters (one required) with no schema descriptions, the description is incomplete. It fails to distinguish the tool or provide enough context for correct invocation.

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 0%, and the description does not mention any parameters. The required parameter 'path' is left entirely unexplained, forcing the agent to guess its meaning (presumably an output file path).

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 the verb 'Export' and the resource 'DXF', making the purpose immediately clear. However, it does not differentiate from other export siblings beyond the format name, which is minimal differentiation.

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 over other export options like rhino_export_obj or rhino_export_stl. The only hint is 'bridge required', but it does not explain when that bridge is applicable or alternatives.

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