rhino_check_mesh

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so basic safety is covered. The description adds specific behavioral context by listing the quality checks performed, which is beyond the title. However, it does not describe the output format or any preconditions, though the output schema likely covers the return.

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?

A single, efficient sentence that front-loads the verb and lists the checks. There is no redundancy or filler, making it well-structured and immediately scannable.

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?

The tool is simple (one parameter) and an output schema exists, so return format is not necessary. However, the lack of usage guidance and the ambiguous parameter semantics make the description incomplete for correct invocation. An agent might not know that the GUID must be a mesh or when to prefer this over sibling tools.

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 only parameter is 'guid' with schema description 'Object GUID', and schema coverage is 0%. The tool description does not clarify that the GUID must reference a mesh object, nor does it explain the expected input semantics. With such low schema coverage, the description fails to compensate, leaving the agent uncertain about what to provide.

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 specific verb ('Check') and resource ('mesh quality'), and enumerates the exact checks performed (closed, normals, degenerate faces, naked edges). This clearly distinguishes it from the broader 'rhino_check_objects' and the more focused 'rhino_get_naked_edges', so an agent can differentiate without opening schemas.

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 is provided on when to use this tool versus alternatives like rhino_check_objects or rhino_get_naked_edges, nor any exclusions or prerequisites. The description only states what it does, leaving the agent to infer the appropriate context.

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