wp_list_media

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

With no annotations, the description should disclose behavioral traits such as that it is a read-only operation, supports pagination, or requires certain permissions. The description provides none of this, leaving the agent to infer behavior from the schema alone.

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, short sentence that efficiently conveys the core purpose. While minimal, it avoids unnecessary detail and is front-loaded. It earns a 4 as it is concise without being vague, though it could incorporate more context without becoming verbose.

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 lack of output schema and the presence of pagination/filtering parameters, the description should mention that results are paginated or can be filtered. The description is incomplete as it provides no context about the behavior or output structure beyond what the schema offers.

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 input schema has 100% description coverage for all 4 parameters (per_page, page, media_type, search). The description adds no extra meaning beyond the schema, which is acceptable but not exemplary. Baseline score of 3 is appropriate.

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 'List media library items' clearly states the tool's action (list) and resource (media library items). It distinguishes from sibling tools like mcp_get_media which retrieve a single item, making 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?

No guidance is provided on when to use this tool versus alternatives (e.g., mcp_get_media for single item, mcp_sideload_media for uploads). There is no mention of prerequisites, limitations, or recommended scenarios.

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