wordpress_list_pages

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

No annotations provided, so description carries full burden. It successfully discloses pagination behavior and metadata inclusion in return values, but omits read-only safety, authentication requirements, rate limits, and error conditions.

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 with two sentences and no redundancy. However, given the severe lack of schema documentation and annotations, this brevity becomes a liability rather than a virtue.

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?

Inadequate for a 4-parameter tool with 0% schema coverage, no annotations, and no output schema. The minimal description fails to compensate for missing structured metadata, particularly regarding parameter semantics and return value structure.

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% (no parameter descriptions), yet the description adds zero semantic context for the 4 parameters including the required 'site' parameter or the 'status' filter options. Critical gap.

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?

Clear verb-resource combination ('List WordPress pages') identifies the specific content type. However, it fails to explicitly distinguish from siblings like wordpress_list_posts or wordpress_list_custom_posts, which is critical given the sibling tool density.

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 versus alternatives (e.g., when to use list_pages vs list_posts or list_custom_posts). The [UNIFIED] prefix provides no actionable context for selection.

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