toggle_overlay

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

Description details that clicking objects highlights them with wireframe and that the overlay resets on reload. Consistent with annotations (idempotentHint=true) and adds useful behavioral context beyond the 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?

The description is mostly concise but has slight redundancy: 'Debug only — page reload will reset' appears twice. Could be tightened into a single paragraph.

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?

The description covers the overlay's features and interaction, and no output schema is needed for a toggle tool. It answers what the tool does and its side effects (visual overlay) sufficiently.

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 baseline is 3. The description adds value by explaining the toggle behavior (show/hide/toggle) and the overlay contents, complementing the schema's parameter description.

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 it 'Toggle a lightweight scene inspector overlay' and lists what it shows (FPS, draw calls, etc.), distinguishing it from sibling tools like 'overlay_selected' or 'perf_monitor' which have different purposes.

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?

Specifies 'Debug only' and warns that 'page reload will reset,' indicating appropriate context. Does not explicitly list alternatives or when not to use, but the purpose is clear enough.

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