wordpress_create_page

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

No annotations provided, so description carries full disclosure burden. Mentions HTML support, hierarchical parents, and URL slug customization, but fails to declare mutation behavior (write operation), return values (created page ID/object), error conditions, or idempotency. Missing critical safety context for a creation tool.

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?

Single sentence, front-loaded with action. Efficient structure. Minor deduction for '[UNIFIED]' prefix which adds no semantic value for the agent.

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?

Creation tool with 6 parameters, 0% schema coverage, no annotations, and no output schema. Description omits return value structure (critical for verification), required parameter formats, and error scenarios. Adequate as a title but insufficient as standalone documentation.

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 has 0% description coverage requiring description to compensate. Mentions content (HTML), parent, and slug parameters indirectly. Fails to describe required parameters 'site' (format unclear: URL or ID?) and 'title', or optional 'status' (draft/publish?). Insufficient for 6-parameter tool with no schema documentation.

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?

Clear verb (Create) + resource (WordPress page) combination. Explicitly distinguishes from sibling tools like wordpress_create_post by specifying 'page' resource type. The '[UNIFIED]' prefix is extraneous but doesn't obscure the clear purpose.

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?

No explicit guidance on when to use vs alternatives (e.g., wordpress_update_page for existing pages). No mention of prerequisites like site authentication. Feature list (HTML, parents, slugs) implies capabilities but not selection criteria.

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