mesh_render

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

No annotations exist, so the description carries the full burden. It does disclose the output format (PNG) and that rendering is for inspection, but says nothing about where the file is written, whether it overwrites existing files, or what the call returns (a path? nothing?), which matters for a file-producing tool.

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 sentences, zero waste: the action and output come first, then the one parameter that genuinely needs enumeration. Nothing is redundant with the schema.

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?

No annotations and no output schema, yet the description still covers the essential gap: the views enumeration. The remaining ambiguity (where the PNG lands) is a real gap but minor.

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 coverage is 0%, so the description must compensate. It does well for `views` (lists all seven valid values and the comma-separated format, which the schema lacks), but adds nothing for `path` and `size_px` beyond their obvious names and defaults.

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?

States a concrete verb+resource and output artifact: 'Gera um PNG da malha para inspeção visual'. It distinguishes itself implicitly from analysis siblings (mesh_measure, mesh_check_printability) by framing the output as a visual artifact, but never names or contrasts those siblings 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?

'para inspeção visual' implies the when (visual QA rather than numeric measurement), but there is no explicit guidance on when to prefer this over mesh_check_printability or mesh_measure, and no prerequisites stated for `path` (must the mesh already be loaded/opened?).

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