wp_unload_region

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the basic operation and gives an example; it does not explain what 'matching' means across the six parameters, whether unloads affect the persistent world partition state, or what consequences the operation has on the editor.

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 short, front-loaded with the action, and includes a useful example and a KB reference. No unnecessary filler is present, though the lack of structured parameter guidance is a completeness issue rather than a conciseness issue.

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 has six optional parameters with zero schema documentation and no annotations, yet the description provides no semantics for five of them and no selection-combination rules. Although an output schema exists and a KB link is given, the description alone is far too thin for an agent to invoke this tool correctly with anything beyond the single labeled example.

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% and none of the six parameters (max, min, exact, label, center, extent) are explained. The single example mentions label but does not clarify the meaning or interaction of the other parameters, so the description fails to compensate for the schema's complete lack of semantic information.

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 states a specific verb ('Unload') and a specific resource ('matching World Partition editor region loaders'), making the core action clear. The example further clarifies usage with a real label. However, it does not explicitly differentiate this tool from its sibling wp_load_region, so it stops short of a 5.

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 explicit guidance is given about when to use this tool versus alternatives such as wp_load_region. The example implies a usage pattern, and the KB link is a pointer, but there is no stated condition, exclusion, or comparison that helps an agent choose this tool confidently.

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