create_wiki_page

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

With no annotations, the description usefully discloses that this is not create-only: an existing page at the path will be updated. It does not clarify whether existing content is replaced, whether history is preserved, or what permissions and failure conditions apply, leaving important mutation behavior unspecified.

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 short sentences state the primary operation and then the important existing-page exception. The wording is direct, front-loaded, and contains no unnecessary repetition.

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?

Together with the fully documented flat schema, the description is sufficient for a basic invocation and communicates its central upsert behavior. It is less complete for correct tool selection and safe mutation because update_wiki_page overlap, overwrite semantics, and result behavior remain unexplained, with no output schema to fill the latter gap.

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 schema already explains all six parameters, including Markdown content, page-path creation, and optional identifiers. The description adds a useful connection between pagePath and update-on-existing behavior, but little additional parameter-level detail 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?

The description clearly identifies the action and resource: creating a page within a wiki, rather than creating the wiki itself. The existing-path update behavior is useful, but the description does not distinguish this tool from the sibling update_wiki_page despite their overlapping capabilities.

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 page-existence condition provides some usage context by establishing create-or-update behavior at the supplied path. However, there is no explicit guidance on when to choose this tool over update_wiki_page, or any prerequisites such as identifying the wiki or checking whether the page exists.

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