wp_list_comments

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

No annotations provided, so the description carries full burden. It only says 'List comments' with no disclosure of behavioral traits like pagination, default sorting, or whether it returns all statuses. The schema parameters hint at filters, but the description adds nothing.

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?

Extremely concise at two words, but this is under-specification, not efficient conciseness. It lacks structure and fails to convey important information that a longer description would provide.

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 has 4 parameters, pagination, and filtering, the description is incomplete. No mention of return format, output schema, or how filters combine. The schema helps but the description should provide an overview like 'Returns a paginated list of comments, optionally filtered by post ID or status.'

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 description coverage is 100%, so the schema already documents all four parameters (per_page, page, post, status) with descriptions. The tool description does not add any additional meaning or context beyond the name, but baseline is 3 due to high coverage.

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 'List comments' clearly states the action and resource. However, it does not explicitly differentiate from sibling tools like 'wp_get_comment' beyond the verb 'list', but the name itself implies listing multiple items.

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. No context on prerequisites, typical use cases, or when not to use it. Siblings like 'wp_get_comment' are not mentioned.

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