List media

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

With no annotations, the description discloses key behaviors: pagination, optional filtering by MIME type, and the required 'media:read' scope. It does not detail return structure, but covers the main behavioral aspects for a list operation.

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 three concise sentences that each add value: purpose, filtering, and auth requirement. It is front-loaded and free of filler.

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?

The description covers purpose, pagination, filtering, and scope, but omits return format details. Given no output schema, a bit more specificity about the response would improve completeness, but the essentials are present.

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 schema covers all three parameters with detailed descriptions (page, type, perPage). The description's mention of 'MIME type prefix (e.g. 'image')' merely repeats the schema's existing example, adding no additional semantic 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 'Lists items in the media library' with a specific verb and resource, and distinguishes from sibling list tools (list_posts, list_comments, list_members) by specifying 'media library' and the MIME type filter.

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 provides clear context by defining the resource as 'media library' and noting optional MIME type filtering, making its intended use obvious. It does not mention alternatives or exclusions, but none are necessary given the distinct resource.

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