ui-redraw

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It only says 'Request', implying a non-destructive operation, but fails to mention that it might be a no-op if the timer isn't available, any side effects, or whether it returns anything. This is insufficient for an action tool.

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 concise sentence, which is structurally fine, but it is under-specified. It lacks any structure that would help an agent parse conditions or usage, so while efficient, it does not pack enough information into its 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?

The tool is simple with only two optional parameters, but the description fails to provide essential context such as effect, return value, or failure modes. The absence of an output schema means the description should at least hint at no return or success/failure signaling, which it doesn't. Overall, it is barely adequate for an agent to use correctly.

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?

The schema has 0% description coverage, and the description entirely ignores the parameters 'type' and 'iterations'. There is no explanation of what redraw timer types mean or how iteration count affects behavior, leaving the agent to guess solely from defaults and names.

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 requests a Blender UI redraw, with a specific condition (when wm.redraw_timer is available). This is a specific verb+resource, and there are no sibling tools with a similar intent, so it stands out. However, it could be more precise about what a 'redraw' accomplishes.

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?

No guidance is provided on when to use this tool versus alternatives. The mention of 'when wm.redraw_timer is available' is a technical prerequisite, not a usage context. There is no discussion of scenarios like forcing a refresh or after model changes, nor any exclusions.

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