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

The description declares a mutation ('MUTATES'), consistent with destructiveHint=true, and adds the transport (JSON POST) and return value ('Returns the created category') beyond the annotations. The most valuable disclosure is that the API itself requires six fields (type, project_id, url_hash, name, visibility, status) even though the schema marks only two as required — a real behavioral gap surfaced in prose. It stops short of saying what happens on duplicate url_hash or whether the node is placed under a parent.

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?

One dense, front-loaded block that opens with the mutation warning and the resource before listing API requirements. Every sentence carries information, though the telegraphic API-requirement list reads more like a spec dump than prose.

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?

Covers mutation semantics, endpoint, required API fields, the escape hatch for extra fields, and the return value despite there being no output schema. Missing only edge-case behavior (duplicates, tree placement) for a 7-parameter write tool with a nested `fields` object.

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 the baseline is 3 and the schema already documents every field including the `fields` merge behavior. The description's enumeration of API-required fields adds some meaning by contradicting the schema's narrower required list, but adds no format or value examples beyond that.

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 and resource with scope: 'creates a new category (a node in the article tree)', plus the underlying endpoint POST /category.json. This clearly separates it from knowledgeowl_update_category (modify) and knowledgeowl_create_article (different resource).

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 verb 'creates' and the 'MUTATES KnowledgeOwl data' framing, and it explains how to send extra fields via `fields`. However, it never explicitly says when to prefer this over update_category, nor does it mention prerequisites such as a valid project_id or uniqueness constraints on url_hash.

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