wp_posts_create

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

No annotations exist, so description carries full burden. It discloses default draft status, publish tier requirement, and scheduling behavior, which is useful. However, it omits return value expectations, permission requirements beyond publish tier, and side effects beyond post creation.

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?

Two sentences, first is direct and front-loaded. Every clause adds value, no filler.

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?

Tool has 13 parameters and no output schema or annotations, yet description addresses only status behavior. Many parameters (meta, sticky, excerpt, featured_media) and expected response are left undefined, making it insufficient for full autonomous use.

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 and 13 parameters, description only clarifies status and date. Required title/content and other fields like meta, sticky, format remain unexplained, leaving significant ambiguity.

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?

Description uses specific verb 'Create' with resource 'blog post', clearly distinguishing from update/publish/schedule tools. It even explains how to achieve publish/schedule via status field, reinforcing its role as the create action.

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 clear context for status values: default draft is safe, publish requires publish tier, future schedules with date. Doesn't explicitly name alternative tools but the guidance prevents misuse and orients the agent toward appropriate statuses.

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