wordpress_create_custom_post

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

Lacks annotations entirely, so description carries full burden. Mentions support for 'custom fields/meta data' but fails to disclose if this requires specific capabilities, what the return value contains, error conditions, or that this is a write operation affecting database state.

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?

Brief two-sentence structure is efficient, but the '[UNIFIED]' prefix is noise without context. Given zero schema coverage and six parameters, the description is overly terse rather than appropriately 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?

Severely inadequate for a six-parameter creation tool with no annotations and no output schema. Missing critical details: parameter formats, authentication requirements, WordPress-specific constraints, and success/failure behaviors.

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 coverage is 0%, requiring heavy description compensation. While it hints at the 'meta' parameter supporting custom fields, it provides no guidance on the 'site' identifier format, valid 'status' values (draft, publish, etc.), or expected 'post_type' format (slug vs label).

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?

States specific action (Create) and resource (custom post type), distinguishing it from the sibling 'wordpress_create_post' by explicitly targeting custom post types. However, it assumes familiarity with WordPress 'custom post type' terminology without elaboration.

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 this versus 'wordpress_create_post' or other creation tools. No mention of prerequisites (e.g., existing custom post type registration) or workflow context.

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