ui.redraw

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

Without annotations, the description must disclose behavioral traits. It mentions a prerequisite (wm.redraw_timer availability) but fails to describe side effects, return behavior, or error handling. An agent cannot infer whether the call is safe, blocking, or what happens if the timer is unavailable.

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 a single sentence, efficiently conveying core purpose and a key condition. While concise, it omits parameter information, but the structure is not verbose. It earns its place by being direct, though could be more informative without losing brevity.

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?

Given the tool has two parameters, no output schema, and no annotations, the description is insufficiently complete. It does not explain how to use the parameters, what the tool returns, or handle edge cases. An agent would struggle to invoke this tool correctly without additional context.

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 0%, so the description must explain parameter semantics. However, it does not mention either parameter (type or iterations). The agent has no context on what 'type' values are acceptable or how 'iterations' affects the redraw, relying solely on schema defaults and constraints.

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 triggers a UI redraw in Blender, specifying the action 'Request a Blender UI redraw' and a condition 'when wm.redraw_timer is available'. It distinguishes itself from sibling tools with a unique function and purpose.

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 implicitly suggests usage when the wm.redraw_timer is available, but does not explicitly state when to use this tool versus alternatives, nor does it provide when-not-to-use guidance. No sibling tools with similar functionality are mentioned, limiting usage context.

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