wordpress_list_comments

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

No annotations are provided, so the description carries the full burden. It discloses the return behavior ('List of comments with pagination info') and filter options, which is sufficient for a read-only listing operation. It does not state read-only explicitly, but that is inherently clear from the verb 'List'.

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 well-structured with an Args list and a Returns line. Each parameter line is concise, includes defaults and constraints, and there is no filler or repetition of schema information.

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 seven optional parameters and an output schema present, the description covers all parameters, their defaults, the per_page maximum, and the return type ('List of comments with pagination info'). This is sufficient for a complete understanding of the tool.

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 input schema has zero description coverage, but the description thoroughly explains every parameter: 'post' filters by post ID, 'status' enumerates allowed values, 'search' searches content, 'page' and 'per_page' control pagination with defaults and max, and 'orderby'/'order' specify sorting. This adds critical meaning the schema lacks.

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 a specific verb 'List' and identifies the resource 'WordPress comments' with filtering, clearly distinguishing it from sibling tools like wordpress_get_comment (single comment retrieval) and wordpress_moderate_comment (moderation). The purpose is unambiguous.

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 implies usage for retrieving multiple comments with optional filters and pagination. It does not explicitly mention alternatives or when-not-to-use, but the list-vs-single nature of the tool is obvious from the name and description, providing clear context without exclusions.

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