set_procedural_mesh_section_visible

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

Annotations already declare idempotentHint=true, destructiveHint=true, and readOnlyHint=false. The description adds useful semantic detail beyond them: it specifies the operation sets the bSectionVisible flag directly (not a flip), which clarifies the idempotent behavior, and supplies a return shape in the absence of an output schema.

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 tightly written sentences, with the core operation front-loaded and the return shape appended. No wasted clauses.

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?

For a low-complexity 4-parameter mutation tool, the description covers the operation, the idempotent semantics, and the return shape (valuable since no output schema exists). Annotations carry the safety profile. Minor gap: no guidance on actor_label/component_index resolution, though the schema handles those.

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 100%, so the schema already documents all four parameters. The description adds little parameter-level meaning beyond noting 'a single section', so the baseline 3 applies.

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 (set visibility/toggle) and resource (a single section on a procedural mesh component), and clarifies the scope is 'a single section'. This distinguishes it clearly from siblings like get_procedural_mesh_section_visible, update_procedural_mesh_section, and set_procedural_mesh_material.

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 'single section' wording implies the granularity of use, but there is no explicit when-to-use, when-not-to-use, or named alternative (e.g., how it differs from update_procedural_mesh_section). Usage must be inferred from the name and scope qualifier.

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