enable_meshing

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

The description discloses the toggle behavior (enable/disable) and use cases, which aligns with the readOnlyHint=false annotation. However, it lacks deeper behavioral context such as whether disabling removes existing meshes, performance impact, or permission requirements.

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 description is two sentences: the first states the action and resource, the second lists use cases. It is concise, front-loaded, and contains no unnecessary words.

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?

Given the tool has 9 parameters including a nested object, the description is succinct but covers the core functionality. The full schema documentation compensates for lack of detail about optional parameters. Slightly more context about when to adjust parameters would improve completeness.

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?

With 100% schema description coverage, the schema already fully documents all parameters. The description adds no additional insight beyond the schema, so a baseline of 3 is appropriate.

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 clearly states the verb (Enables or disables) and resource (spatial meshing), and explicitly lists use cases (occlusion, physics collisions, spatial understanding). It distinguishes from sibling tools like 'enable_hand_tracking' or 'configure_occlusion' by focusing on mesh generation.

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 provides no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. It simply states the function, leaving the agent to infer usage context.

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