mbs_list_pages

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

With no annotations, the description carries the full burden. 'List' implies a read-only operation, and the optional search behavior is noted, but the description does not explicitly state that it is non-destructive, or disclose any other behavioral traits such as return format or pagination details beyond what the schema provides.

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 a single sentence that is front-loaded with the core action and resource. Every word contributes ('WordPress pages', 'statistical report pages', 'optional search'), with zero redundancy or fluff.

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?

This is a simple list tool with no output schema or annotations. The description, combined with the parameter schema, provides enough for an agent to select and invoke the tool. It could be slightly more complete by describing the response shape, but for a straightforward list operation, this is acceptable.

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% with all three parameters (page, search, per_page) already described. The description's mention of 'optional search' adds no extra meaning beyond the schema, so it does not compensate or add value.

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 a specific verb ('List') and resource ('WordPress pages'), and distinguishes from siblings like mbs_list_posts by clarifying these are 'statistical report pages.' This makes the purpose 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 implies usage (when you need to list pages with optional search) but does not explicitly mention when to use this tool vs alternatives like mbs_get_page or mbs_list_posts. No exclusions or explicit alternatives are provided, so guidance is only implied.

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