export_component_mesh

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

No annotations are provided, so the description carries the full behavioral burden. It reveals only that output is base64-encoded; it says nothing about required session state, permissions, failure modes for unsupported formats, or whether the operation is read-only or has 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?

It is a single waste-free sentence, front-loaded with the verb and resource. However, for a four-parameter export tool it is arguably undersized rather than appropriately sized, leaving no room for the context an agent needs.

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?

With no annotations, no output schema, and 0% schema coverage across four parameters, the description is far too thin. An agent cannot tell how to populate meshing_options, what the formats imply, or what conditions must hold before export succeeds.

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%, so the description should compensate but mentions none of the four parameters. In particular 'meshing_options' (an arbitrary numeric map with null default) and the meaning of 'session_id' versus 'component_uid' are entirely unexplained.

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 uses a clear verb+resource pairing ("Export a component mesh") and adds the output form (base64-encoded content). The resource distinguishes it implicitly from siblings like export_configuration_cad, 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?

There is no guidance on when to use this tool versus export_configuration_cad or the other export/list siblings, and no stated prerequisites such as whether a mesh must already exist or whether a session must be open.

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