production.game_mesh_validate

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

Annotations declare readOnlyHint=false and idempotentHint=false, implying the call produces new artifacts or writes state on each run, yet the description says nothing about what is written, where results land, or whether the mesh itself is touched. The one genuinely useful disclosure is that gates are concrete and no arbitrary quality score is returned, which sets expectations about output semantics. For a non-read-only tool with zero annotation coverage of side effects, that is a real gap.

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 front-loaded clause with no filler; the aggregation scope leads and the 'no arbitrary quality score' caveat follows. It is dense with domain jargon, which costs a little readability but no sentence is wasted.

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 need not be restated, and annotations carry the safety flags. Still, the required parameter is undocumented in both schema and prose, and the side-effecting behavior implied by readOnlyHint=false and idempotentHint=false is unexplained. For a three-parameter aggregate validator, the description leaves too much unexplained.

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 three parameters, and the description adds no meaning to any of them. The required 'relationship' parameter, the free-form 'options' bag, and 'operation_id' are all left undefined; the agent must guess what 'relationship' identifies. The list of gate categories gives only faint hints about what 'options' might toggle.

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 the resource (game mesh) and the aggregation scope explicitly: topology, fidelity, deformation, attributes, UV and bake gates. That distinguishes it from the narrower siblings like game_mesh_validate_triangulation, game_mesh_validate_tangents, uv_validate and bake_validate. It never states the outcome form (per-gate pass/fail report), but the verb+resource+scope is clear enough for an agent to route.

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 word 'aggregate' implies this is the roll-up check to run instead of the individual single-gate validators, but that choice is never made explicit and no prerequisites are named. Nothing says when NOT to use it, nor whether it subsumes or duplicates the sibling triangulation/tangent/bake validators. Usage is inferable but not guided.

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