List media

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

The description discloses the 'newest first' ordering, which is a meaningful behavioral detail. However, since no annotations are provided, the description carries the full burden and fails to mention pagination behavior (page/per_page) or other side effects, leaving transparency incomplete.

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, front-loaded sentence with no redundant or filler content. Every word adds value: it identifies the action, the resource, and the default ordering.

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?

With no annotations, no output schema, and only 20% parameter coverage, a more detailed description is necessary. The description omits filtering and pagination semantics and does not explain what fields are returned, leaving the agent under-informed for a tool with 5 parameters.

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 only 20% (only the 'site' parameter is described), and the tool description adds zero information about the other parameters (page, per_page, search, media_type). The description does not compensate for the low schema coverage, forcing the agent to rely on parameter names alone.

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 the tool's purpose with the verb 'List' and identifies the specific resource 'media library', distinguishing it from sibling list tools such as wp_list_users or wp_list_content. It also adds the ordering detail 'newest first', which gives useful scope.

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?

There is no explicit guidance on when to use this tool versus alternatives like wp_list_content or wp_list_users. The description implies usage by naming the media library but lacks exclusions, prerequisites, or alternative recommendations.

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