Rebuild / redraw

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

Annotations cover the safety profile (readOnly=false, idempotent=true, destructive=false), and the description adds meaningful behavior beyond them: 'Regenerate' recomputes all element geometry while 'Redraw' only repaints. That distinction is exactly what an agent needs and is not derivable from the enum alone.

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?

A single sentence, front-loaded with the core action, with the mode nuances parenthetically folded in. No filler; every clause earns its place.

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 zero-required-param refresh tool with no output schema, the description covers what the tool does, the effect of each mode, and when to use the heavier option. Return behavior is not described, but nothing critical for correct invocation is missing.

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% but the schema only lists the enum values with 'Default Rebuild'. The description adds real semantics for each value — full geometry recomputation vs. repaint — which the schema does not convey.

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 and resource ('Refreshes the current (front) window') and then names and disambiguates all three distinct modes. No sibling tool covers view refresh, so the agent can identify this immediately.

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?

Explicitly tells the agent when to pick 'Regenerate' ('use after library/parameter changes or when the display looks stale') and distinguishes 'Redraw' as repaint-only, which is real selection guidance. It does not state when NOT to use the tool or name any alternative, keeping it short of a 5.

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