wordpress_list_pages

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

No annotations provided, so description carries the burden. It says '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 structured with 'Args:' and 'Returns:' sections, listing each parameter concisely with its purpose. It's front-loaded with a clear summary sentence. No fluff, every sentence adds value.

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 schema covers all parameters and the output schema exists, the description adds context by explaining filtering and pagination. It states 'with pagination info' which is useful. It might mention that results are ordered but not necessary. It's complete for a list tool. Could mention common use cases but not required. Score 4 because it doesn't explicitly distinguish from list_posts or list_categories, but it's clear enough.

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 description explicitly defines each parameter's meaning (e.g., 'Filter by status', 'Page number'), and it also specifies allowed values for status like 'publish, draft, private, future' and for orderby, though orderby values are listed. Since schema coverage is 0%, the description fully compensates by describing all parameters and their purpose. It also mentions defaults for some, though not all. This is strong.

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 clearly states what the tool does: 'List WordPress pages with filtering and pagination.' It uses a specific verb (list) and resource (WordPress pages), and the mention of filtering and pagination distinguishes it from sibling tools like get_page, create_page, or get_post.

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 lists parameters that imply usage scenarios (filter by status, search, etc.), providing clear context. However, it does not explicitly mention when not to use this tool or point to alternatives like wordpress_list_page_revisions or wordpress_get_page. Still, the intent is unambiguous, so slight deduction for missing exclusions.

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