toggle_wireframe

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

The description adds value beyond annotations by explaining that the change is runtime-only and resets on page reload. This aligns with idempotentHint and clarifies the non-destructive nature despite readOnlyHint being false. No contradictions 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?

Two concise, front-loaded sentences with zero waste. Every word adds value, clearly stating action, scope, and context.

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 is complete for a simple toggle tool with no output schema. It covers purpose, usage context, behavior (temporary), and parameter scope. Could be enhanced by mentioning that it affects all materials when no object is specified, but the current text is sufficient.

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% and all parameters have descriptions. The description ('Toggle wireframe on all materials or a specific object') summarizes the parameters but does not add new information beyond what the schema already provides. 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 clearly states the tool toggles wireframe on materials or a specific object, and specifies it is for runtime visual debugging. It uses a specific verb ('Toggle') and resource ('wireframe'), distinguishing it from sibling tools like 'material_list' or 'set_material_property'.

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 clear usage context ('Runtime only — for visual debugging') and notes that the effect is temporary ('page reload will reset'). It explicitly states 'Debug only', indicating when to use, but does not discuss when not to use or mention alternatives.

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