wordpress_update_comment

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

No annotations provided. Description only states it updates comments without disclosing behavioral traits such as required capabilities, reversibility of actions, side effects (e.g., notifications), or error conditions.

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 with parentheses listing actions. Front-loaded and efficient, though parentheses could be clearer as a structured list. No wasted words.

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 the tool's complexity (multiple possible update actions) and absence of output schema/annotations, the description is inadequate. Does not explain return values, status, or required permissions. Incomplete for reliable agent 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?

Schema has one parameter (commentId) with 0% description coverage. Description mentions actions not represented in schema, failing to clarify how parameter values map to operations. Does not add meaning beyond what minimal schema provides.

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 clearly states verb 'Update' and resource 'comment', listing specific actions (approve, spam, trash, edit content). However, the listed actions are not reflected in the input schema (only commentId), causing potential confusion about how to specify the desired update.

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 guidance on when to use this tool versus alternatives like wordpress_delete_comment or wordpress_create_comment. Lacks context for selecting appropriate tool among siblings.

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