look_at_mesh

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

With no annotations, the description carries the full behavioral burden and does well: it discloses that the render returns image content, that the image always precedes the JSON summary, and that turntable_frames>0 writes a GIF file for the human and returns its path. It does not cover error behavior or mesh-missing cases, but the key side effect and return ordering are explicit.

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 core render-and-return purpose is front-loaded with bold emphasis, and the remaining guidance is compact. The structure is easy to scan, though slightly informal.

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 render tool with no output schema and no annotations, the description adequately explains the return format and two parameters. However, six of eight parameters have no semantics anywhere, and there is no mention of prerequisites or failure modes, so it is only minimally sufficient.

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% across 8 parameters, so the description must compensate. It only explains views ('four'/'single'/'grid') and turntable_frames behavior; name, size, azimuth, shading, elevation, and wireframe remain entirely undocumented, leaving most parameters opaque.

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 specific verb (render) and resource (model), and frames the purpose as self-verification. It does not explicitly differentiate from sibling check_mesh or describe_model, but the action is unambiguous without opening the schema.

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?

The description recommends 'views: four' as the starting point, implying primary usage. However, it gives no explicit when-not condition or comparison to siblings like check_mesh, leaving the agent to infer when rendering is preferable.

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