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

Annotations already declare this is a non-read-only but non-destructive mutation, so the safety profile is covered. The description adds that ALL zones are refilled (not a selective refill), which is useful scope context. However, it says nothing about the job's asynchronous nature, which only surfaces in the wait_s schema text.

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 front-loaded sentence with no filler, and the scope word 'every' is well placed. It is arguably too terse for the async behavior, but there is no wasted text.

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 low-complexity two-parameter tool with a fully documented schema and no output schema, the description is close to sufficient. The main omission is that this spawns a pollable job, which the agent must piece together from the wait_s schema description rather than the tool description.

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 100%, so both parameters (design_id and wait_s, including the follow-up with get_board_job) are fully documented in the schema. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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 (refill) and resource (every copper zone) and names the underlying engine (KiCad's zone filler), which implies regeneration rather than zone creation. It is distinguishable from set_zones by the word 'refill', but the description never explicitly differentiates itself from that sibling.

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?

There is no statement of when to use this tool versus alternatives like set_zones, route_board, or tidy_copper, and no mention of prerequisites such as needing an imported design or routed nets first. Usage is only implied by the verb.

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