Create Wiki Page

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

The description warns that GitHub-specific Markdown extensions will not render, revealing an important non-obvious behavior and pointing to a YFM cheatsheet resource. Annotations declare openWorldHint=false and destructiveHint=false, so the description adds useful context without contradiction.

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 sentences, front-loaded with the core action, and the second sentence provides a specific, high-value clarification. No filler.

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?

The tool has a clear purpose, output schema, and annotations. The main gap is conflict behavior (e.g., what happens if the slug already exists), but the YFM cheatsheet link and schema make the description reasonably complete.

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?

All three parameters have descriptive schema entries with 100% coverage, so the schema already documents parameter meanings. The description adds a useful YFM note for the content parameter but does not alter slug or title semantics.

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 opens with 'Create a Yandex Wiki page,' which is a specific verb+resource statement. It clearly distinguishes page_create from siblings like page_update, page_delete, and page_get by focusing on creation.

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?

There is no explicit guidance on when to use this tool versus page_update or page_clone. The YFM formatting note implies content requirements but does not address when to choose page_create over alternatives.

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