wp_cpt_list

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'List items' and gives parameter context; it does not disclose return format, pagination behavior, authentication requirements, or whether the operation is read-only. This is a significant gap.

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?

Two focused sentences front-load the core action, provide a concrete example, and give an exclusion. No filler or redundant restatement of the schema.

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?

Without an output schema, the description should explain what the response looks like (e.g., array of items, pagination metadata) and any constraints on the listed parameters. It only covers the post_type mapping and built-in alternatives, leaving the tool's full behavior under-specified for a 7-parameter list operation.

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 0% for 7 parameters. The description adds meaningful guidance for post_type (must match rest_base), but leaves page, order, search, status, orderby, and per_page unexplained. Conventional names help but the description does not compensate for the complete lack of schema documentation.

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 identifies the tool as 'List items of any registered Custom Post Type', which is a specific verb and resource. It also differentiates from built-in posts/pages by directing users to wp_posts_list / wp_pages_list.

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 states when to use the tool (for custom post types) and when to prefer alternatives (wp_posts_list / wp_pages_list for built-in posts/pages). It also provides a concrete prerequisite that post_type must match the rest_base from wp_get_post_types.

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