wordpress_create_comment

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

No annotations provided, so description carries full burden. Mentions 'moderation status' but fails to explain behavior: what 'hold' (the default) means, that comments may await approval, side effects on post comment counts, or the response format. Missing critical behavioral context for a write operation.

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 efficient sentences with no fluff beyond the '[UNIFIED]' tag. Information is front-loaded with the action in the first sentence and capabilities in the second. Appropriately sized but loses a point for the unnecessary metadata prefix.

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?

Inadequate for a 6-parameter mutation tool with zero schema descriptions and no output schema. Missing: valid status enum values, site format expectations, return value description, error scenarios, and authentication requirements. Description covers perhaps 30% of what an agent needs to invoke this correctly.

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 mentions 'author information' and 'moderation status' (covering 3 optional params conceptually), it completely omits the 3 required parameters (site, post_id, content) and provides no valid values for status or format guidance for site strings.

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') + specific resource ('WordPress comment') + context ('on a post'). The '[UNIFIED]' prefix is noise but the core statement effectively distinguishes this from siblings like directus_create_comment and wordpress_update_comment.

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?

Implies usage through feature description ('Supports author information and moderation status') but provides no explicit guidance on when to use this vs wordpress_update_comment, prerequisites like requiring a valid post_id, or what 'moderation status' values are valid.

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