media_list

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructivHint=false and openWorldHint=true, so the safety profile is fully covered by structured data. The description adds nothing beyond that: no mention of default page size, ordering, pagination behavior, or what 'media library items' contain in this WordPress context. It contributes no behavioral value the agent doesn't already have.

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?

A single short, front-loaded sentence with no padding or filler. It is appropriately sized, though its brevity reflects missing content rather than efficient packing.

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 simple read-only list tool with annotation coverage and no output schema, the minimum needed to invoke it correctly is present. However, an agent gets no hint about ordering, pagination limits, or the shape of returned media items, which would matter when choosing between this and other list tools.

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?

There is a single optional parameter (limit) with 100% schema description coverage, so the schema already documents it. The description adds no default value, max cap, or ordering semantics, so the baseline of 3 applies.

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 verb plus resource ("List media library items"), so the basic operation is clear, but it largely restates the tool name and offers no distinction from the many other list siblings (post_list, file_list, term_list, plugin_list). An agent cannot tell from the text alone why it would pick this over those.

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 when-to-use, when-not-to-use, or alternative-routing guidance. With a dozen sibling list tools in the set, the absence of any selection criteria is a real gap.

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