viewport_toggle_grid

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

Annotations already indicate a mutating tool (readOnlyHint=false, destructiveHint=true). The description adds useful scoping to the active viewport and maps show=true/false to visibility, but it does not clarify what the destructive hint refers to or whether the setting persists. No contradiction with annotations.

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 short, front-loaded with the main verb and resource, and contains no fluff. The Chinese and English halves are redundant with each other, but that is justified for a bilingual tool.

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 tool with one optional boolean parameter and no output schema, the description sufficiently covers the target scope and parameter effect. It omits return values and side-effect details, but those are minor for a grid-visibility toggle.

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 100%, so the boolean 'show' parameter is fully documented. The description's show=true/false sentence mostly restates the schema and adds no format, default, or edge-case information, so the baseline 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 states a specific verb and resource: show or hide the active viewport grid. This distinguishes it from other viewport tools like viewport_capture, viewport_set_shading, and viewport_set_view, and the parameter mapping is clear.

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 active-viewport-grid scope implies the use case, but the description provides no explicit guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. For a simple toggle this is adequate but not instructive.

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