Inspect Mesh

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

No annotations are provided, so the description carries the full burden. It does disclose a key behavior: it inspects an existing verified export or automatically creates a temporary STL. However, it does not clarify side effects, error cases, or whether the temporary STL is persisted or only used in-memory.

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 a single, front-loaded sentence with no filler or redundant information. It is concise and readable, though it omits some useful details that would have made it more complete.

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?

For a single-parameter tool with an output schema, the description covers the core action and provides a behavioral fallback. But it lacks alternatives/usage context and leaves ambiguity around what 'inspect' returns and what creating a temporary STL implies for the project state.

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?

The schema has 0% description coverage and the description does not mention project_id at all. While the parameter name is reasonably self-explanatory, the description adds no meaning beyond the schema, failing to compensate for the low coverage.

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 names a specific verb ('inspect') and resource ('mesh'), and adds meaningful context about inspecting a verified STL/3MF export or creating a temporary STL. It does not explicitly distinguish itself from sibling tools like read_model or check_printability, so it stops short of a 5.

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 about when to use this tool versus alternatives, nor any stated conditions or exclusions. The description implies it is used for mesh inspection but does not explain when an agent should choose it over read_model, export_model, or render_preview.

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