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

Annotations already indicate this is a mutating, non-idempotent, non-destructive operation. The description adds valuable context beyond those annotations: the slug is checked before the write because it is permanent, slugs are globally unique, and a collision results in a CONFLICT rather than an overwrite. This clarifies a non-obvious failure mode.

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 compact: one identifying sentence plus two sentences of critical slug behavior. It front-loads the core purpose and wastes no words on details already present in the schema or annotations.

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?

With a rich input schema, full parameter coverage, an output schema, and annotations covering read-only/destructive/idempotent traits, the description covers the remaining important behaviors: uniqueness, immutability, and conflict semantics. It could briefly mention when to use this tool versus editing or getting an existing wiki page, but that is a modest gap given the structured richness.

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 each parameter is documented in the schema. The description adds meaning specifically for the slug parameter by stating it is checked before the write, is immutable, and that collisions are CONFLICTs rather than overwrites, complementing the schema's regex and permanence notes. Other parameters are already sufficiently covered by the schema.

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 opening sentence 'Create a wiki page' uses a specific verb ('Create') and resource ('wiki page'), clearly distinguishing it from sibling tools like colony_edit_wiki_page and colony_get_wiki_page. The rest of the description reinforces creation semantics without obscuring the core purpose.

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?

The description gives no explicit when-to-use guidance and does not contrast this tool with colony_edit_wiki_page or colony_get_wiki_page. The permanence of the slug implies this is for new pages, but the agent is left to infer the appropriate usage and no exclusions or alternatives are mentioned.

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