page_create

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

Annotations show it is not read-only, destructive, or idempotent; description adds that parent_id and node_id are mutually exclusive and explains multilingual binding behavior, which goes beyond structured fields.

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 description is concise (~100 words), front-loaded with purpose, and structured into required/optional lists and a separate multilingual note. 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?

Covers most important parameters but misses 'publishing' and does not mention return value (no output schema). Some optional fields like hidden and image_id are listed without elaboration, leaving minor gaps.

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?

With 0% schema description coverage, the description compensates by explaining each parameter's purpose, including constraints (e.g., parent_id vs node_id), examples (content_type values), and nested object (data).

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 'Create a new page' and distinguishes required vs optional parameters. It explains the role of parent_id and node_id, differentiating page creation from sibling tools like page_duplicate or page_update.

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 explicit guidance on when to use parent_id vs node_id for subpages and translations, and notes they are mutually exclusive. However, it does not explicitly mention alternatives like page_duplicate or page_update.

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