Create Wiki Page

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

Annotations indicate readOnlyHint=false (write operation) and idempotentHint=false, but the description adds no behavioral context beyond restating that it creates a page. There's no mention of duplicate slug handling, permissions, or side effects, so it fails to disclose anything beyond what annotations already imply.

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 entire description is a single, concise sentence: 'Create a new wiki_page.' It is efficiently front-loaded and wastes no words. However, it is so minimal that it borders on under-specification, but for pure conciseness it earns a 4.

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 create tool with three required parameters and no output schema, this description is inadequate. It doesn't explain expected return values, possible errors, or usage context. Given sibling tools like wiki_page_update and wiki_page_delete, the description is too sparse to fully inform an agent on how to use the tool correctly.

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 only 33% (only 'slug' has a description), and the tool description provides no parameter information. The description doesn't clarify what 'content' should contain or that 'project' is an ID, leaving the agent with insufficient meaning for two of three parameters.

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 states the verb 'Create' and the resource 'wiki_page', making it obvious that this tool creates a wiki page. It distinguishes from sibling wiki operations (get, update, delete, list) by the create action, though it doesn't mention any specific scope or unique behavior.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites like needing an existing project or how it relates to wiki_page_get_by_slug or other wiki tools. The usage is only implied by the word 'Create'.

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