page_create

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

Explains multilingual behavior and that parent_id and node_id are mutually exclusive. However, fails to disclose what the tool returns (e.g., created page object or ID), required permissions, or potential side effects. Annotations are minimal and do not contradict, but the description lacks crucial behavioral details.

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?

Well-structured: starts with purpose, then lists required and optional params, and ends with multilingual usage. Information is front-loaded but the description could be slightly more concise.

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?

Given the tool's complexity (14 parameters, multilingual use, no output schema), the description covers many aspects but lacks information about return values, error conditions, and prerequisites (e.g., permissions).

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 adds significant meaning by explaining required parameters and most optional ones, especially the critical distinction between parent_id and node_id. However, it omits explanation for 'site' and 'publishing' parameters, which are present in the schema.

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?

Clearly states it creates a new page with required and optional parameters. However, it does not explicitly differentiate from sibling 'page_duplicate' or 'page_add_content', though the context implies creation of a new entity.

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 detailed guidance on using parent_id vs node_id for multilingual pages and notes their mutual exclusivity. But no instructions on when to prefer this tool over 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.