create_page

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

With no annotations provided, the description carries full burden. It discloses that the tool creates a page (mutation), defaults to draft, and returns a preview_url for reviewing drafts. While it doesn't mention auth requirements or destructive behavior, for a creation tool this is sufficient.

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 four sentences with no redundant words. It front-loads the primary action and quickly provides essential details about status behavior, page characteristics, and return values.

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 has 7 parameters (1 required) and an output schema, the description is complete. It explains the default draft, how to publish, the nature of pages, and the return summary including preview_url. The output schema covers return structure, so additional description is unnecessary.

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 0%, but the description adds meaning to key parameters: it explains the default for status, that pages are standalone (so no tags/feed), and that meta_title/meta_description set search-snippet metadata. This compensates fully for the lack of schema descriptions.

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 page from HTML content' and distinguishes pages from posts by noting they are 'standalone (about, contact, …) with no tags or feed placement.' This provides a specific verb+resource and differentiates from sibling tools like create_post.

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 explains the default draft status and how to publish immediately by passing 'status="published"'. It also clarifies that pages lack tags/feed placement, guiding when to use this tool versus create_post. However, it does not explicitly state when not to use it or list alternatives.

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