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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is known; the description adds the crucial semantics behind it: 'The tree is sent whole,' which tells the agent the existing tree is replaced rather than merged. It does not say what happens to existing pages or history when a category is dropped from the tree, which is the main remaining behavioral gap for a destructive mutation.

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?

Three sentences, no filler, with the core action front-loaded and the tree-structure semantics following. The sentences are dense and long, which slightly hurts scannability, but nothing is redundant and every clause carries information.

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 two-parameter mutation tool with no output schema and full schema coverage, the description supplies the conceptual model (wiki pages live in categories, are versioned, have history) plus replacement semantics. It is nearly complete; the missing piece is the effect of removing a category from the tree on existing pages and history.

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 baseline is 3. The description goes beyond the schema by explaining that each node's slug is its path segment and that metadataKeys define the facts a page under that node carries, with a select key becoming a filter on the category page — semantic meaning the schema states only partially ('select keys become facets'). It does not elaborate on the token parameter, but the schema already covers it.

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 and resource ('Give the site a category tree and make it a wiki, or change its tree') and clearly distinguishes the tool from siblings by naming write_site and save_wiki_page as the page-authoring path instead. An agent can tell this is the site-to-wiki conversion/structure tool without opening another schema.

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?

It covers both use cases ('make it a wiki, or change its tree') and routes the agent away from write_site for wiki content, which is a useful sibling distinction. It stops short of explicit when-not guidance (e.g., what to do if the site is already a wiki, or how this interacts with delete_wiki_page/restore_wiki_page), so it is clear context rather than complete routing.

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