production.game_mesh_validate_triangulation

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

Annotations already declare readOnly=false, destructive=false and idempotent=false. The description usefully adds that the triangulation happens on temporary copies, which explains why nothing destructive occurs to the source mesh — real value beyond the annotations. It still says nothing about cost, whether the temp copies persist, or what happens on a mismatch, and with readOnly=false the agent gets no picture of side effects beyond the temp-copy hint.

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?

One sentence, front-loaded with the action and followed by the comparison facets. Dense and waste-free, though the slash-delimited list is terse to the point of being cryptic for the morph/normals terms.

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?

An output schema exists, so return values needn't be explained. But the required 'relationship' parameter is completely opaque, usage context is absent, and the agent has no way to know what to pass or when this validates versus the other game_mesh checks. For a required-parameter validation tool this is under-specified.

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% and the description explains none of the three parameters. The phrase 'two temporary copies' faintly implies that 'relationship' encodes the pairing, but the agent gets no idea what string format 'relationship' expects, nor what 'options' or 'operation_id' control. With zero schema coverage the description was obligated to compensate and does not.

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 and resource: independently triangulate two temporary copies and compare reproducibility, counts, geometry, normals and morphs. That is far more informative than the name alone and separates it in spirit from game_mesh_triangulation_preview (a preview) and game_mesh_validate (general validation). It never names those siblings explicitly, so the differentiation is inferred rather than stated.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as game_mesh_triangulation_preview or game_mesh_validate, even though they sit adjacent in the same game_mesh pipeline. An agent must guess where this QA step belongs in the order of operations.

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