production.mesh_region_define

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

Annotations declare readOnlyHint=false but destructiveHint=false, which could confuse an agent about a 'define' operation. The description resolves this well: 'stores a local manifest with the locked data. Never edits the mesh.' That is genuinely additive context beyond annotations. It stops short of explaining topology-fingerprint mismatch behavior or the non-idempotent 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?

Two tight clauses: the mechanism first, the non-mutation guarantee second. Nothing is padded, though the first clause is densely packed jargon that rewards a domain-aware reader.

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 described, and the description covers storage behavior and non-destructiveness. Still missing: how a topology fingerprint is validated or what happens on mismatch, and what operation_id implies (likely async), which matters for a non-idempotent write tool.

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% and the 'regions' parameter is an unconstrained array of open objects, so the description carries real weight by enumerating vertex_group, face_set, mask and explicit indices as accepted region sources. However, it does not document the shape of each region entry nor the purpose of operation_id, leaving gaps.

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 (Define) and resource (LOCKED/EDITABLE regions), plus the four supported region sources: vertex_group, face_set, mask, explicit indices. It is distinguishable from siblings like mesh_region_verify or character_define_regions by the topology-fingerprint binding and manifest storage, though it never names those siblings directly.

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?

Usage is implied by the vocabulary (define regions, bound to a topology fingerprint, before verification), but there is no explicit when/when-not statement nor a named alternative such as character_define_regions or mesh_region_verify. An agent must infer the ordering in the pipeline.

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