Regenerate one category of a topical map

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

Adds genuinely useful scope information not present in the annotations: only the targeted category is affected, and the rest of the map plus its pillar page are left intact. This complements the idempotentHint=false (each run yields a fresh set). There is mild tension with destructiveHint=false given 'replaces every article,' but the description frames it as scoped regeneration rather than data deletion.

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?

Two sentences, front-loaded with the replacement action and immediately qualified by scope. No filler, and the clarifying sentence about categories 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?

An output schema exists so return values need not be described, and annotations carry the safety profile. The description covers scope and category semantics well; a brief note on prerequisites or failure modes would make it fully complete.

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%, so the baseline is 3. The description goes slightly beyond the schema by explaining the provenance of `category` values ('the category values the map's clusters carry'), which helps the agent supply a valid value; it adds nothing extra for mapId, which the schema already documents.

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 (replaces/regenerates) and a precisely bounded resource: one category's articles within a topical map. It is clearly distinguishable from siblings like create_topical_map and get_topical_map, and the second sentence pins down what a 'category' actually is.

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?

Usage is implied by the semantics of replacement, but there is no explicit when-to-use statement, no prerequisites (e.g., map must already exist and contain that category), and no named alternative. Adequate but leaves routing to inference.

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