List wp-admin menu pages

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

The annotations already mark the tool read-only and non-destructive. The description adds valuable context beyond that by revealing that results come from a snapshot captured on a real admin request and that the snapshot refreshes if needed, which explains potential freshness and non-idempotency behavior.

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 appropriately sized, front-loaded with the action and result fields, and every sentence earns its place. The examples and snapshot note add real value without padding.

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?

For a read-only listing tool with two optional parameters and no output schema, the description is complete: it lists the return fields, explains the plugin filter, and discloses the snapshot behavior. Nothing critical for calling it correctly is missing.

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%, so the schema already documents both parameters well. The description adds a brief note about the plugin filter but does not go beyond what the schema says; site_id is only covered by the schema, which is acceptable at this coverage level.

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 states a specific verb and resource ('List the wp-admin menu and submenu pages'), enumerates the returned fields, and gives concrete use-case examples. It clearly distinguishes itself from navigation-menu tools like list_menus by specifying 'wp-admin menu and submenu pages registered on the site'.

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?

It explains the intended use ('so you can find the screen for a task') and how to narrow results with the plugin parameter. It does not explicitly name alternatives or exclusion conditions, but the context is clear enough for an agent to select it.

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