Read a comment

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

Goes well past the readOnly/idempotent annotations: it discloses error behavior for unknown ids and the required capability. Crucially it surfaces a non-obvious edge case — status can be `false` for post-trashed comments, stored as a distinct value — which an agent could not infer from the schema or annotations.

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?

Front-loads the action, then the return contract, then the edge cases and the sibling redirect — a sensible ordering with no filler sentences. The return-shape portion is dense with semicolon-separated clauses, which costs a little readability.

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?

With no output schema, the description carries the full burden of explaining return values and does so field by field, including formats and timezone. Permission requirement and not-found behavior round out what an agent needs to call 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 100% and the property already says "Comment id, as wp_list_comments returns it," so the baseline is 3. The description's "by id" adds nothing the schema does not already carry about the parameter itself.

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?

Opens with a specific verb and resource ("Get one comment by id") and immediately scopes it to a single record versus the many-record sibling. No ambiguity with wp_list_comments, wp_moderate_comment, or wp_reply_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?

Explicitly routes listing/filtered lookups to wp_list_comments, which is the main plausible alternative. It also names the required capability (moderate_comments), which functions as a gate condition. It stops short of stating when-not-to-use (e.g. to read a comment while moderating), so not a full 5.

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