wp_comments_create

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

With no annotations, the description carries the burden of behavioral disclosure. It reveals a conditional requirement: when 'author' is omitted, 'author_name' and 'author_email' are required. This adds useful context, but it does not disclose other behaviors such as auth requirements, default status, or response format.

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 a single, efficient sentence that provides the essential information without redundancy. It earns its place with the key conditional requirement and reply capability.

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 11 parameters, no annotations, no output schema, and 0% schema description coverage, this sparse description is inadequate. It omits what the response looks like, any error conditions, and details on most parameters. The conditional author rule is helpful, but the tool remains under-specified for correct invocation.

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?

The schema description coverage is 0%, so the description must compensate. It explains the relationship between 'author' and 'author_name'/'author_email', and the role of 'parent' for replies. However, it does not describe the other 8 parameters, relying on their self-explanatory names and types.

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 uses the specific verb 'Create' with the resource 'comment', and clarifies the reply scenario via parent. This clearly distinguishes it from sibling tools like wp_comments_get, update, and delete.

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 clearly indicates when to use this tool (to create a comment or reply via parent), and the verb 'Create' implies it's for creation rather than updating or deleting. However, it does not explicitly mention alternatives or exclusions.

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