create-wiki-page

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

Annotations already declare this is a non-read-only, non-destructive, open-world mutation; the description adds the critical failure mode (400 error without parentPageId), the exact error text, the markdown content format, and the returned fields (id, wikiId, parentPageId, version). That is substantial behavioral context beyond the annotations.

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?

Front-loaded with purpose, then bolded sections for required/optional, the parentPageId pitfall, and the workflow, which makes it scannable. There is mild redundancy: the required/optional lists duplicate the schema, and parentPageId appears in neither list before being discussed separately.

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 6-parameter mutation with no output schema, the description covers prerequisites, ordering, the main failure mode, content format, and return values. Nothing an agent needs to invoke it successfully is missing.

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 still adds real meaning by flagging parentPageId as effectively mandatory and by naming the fields of the referrers/attachment inputs. The required/optional lists largely restate the schema, which caps the score below 5.

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 ('Create a new wiki page') and clearly differs from siblings like update-wiki-page, move-wiki-page, and create-wiki-page-comment. An agent can identify it immediately without opening the 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?

Provides an explicit three-step workflow naming the prerequisite tools (get-wiki-list, get-wiki-page-list) and the condition under which each is needed. It also warns that parentPageId is 'practically required' despite not being in the required array, which is precisely the kind of when-to-use guidance that prevents failed calls.

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