wordpress_get_media

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only says 'Get', implying a read operation, but does not mention pagination behavior, required permissions, rate limits, or what happens when no results found.

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, which is concise, but it is under-specified and omits critical details. Front-loading is acceptable but the brevity sacrifices clarity.

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 simplicity of the tool (pagination only), the description fails to explain how pagination works, return structure, or how to retrieve all items. Sibling tools are similar but not distinguished. With no output schema, the agent is left guessing the response format.

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 coverage is 0% (no parameter descriptions). The description mentions 'filtering by type' but that is not reflected in any parameter; the actual parameters (perPage, page) are not explained. The description adds no value over the bare schema definition.

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 'Get media library files' which clearly identifies the resource and verb. However, it claims 'with filtering by type', but the input schema only includes pagination parameters (perPage, page) and no type filter, making the description misleading about the tool's actual capabilities.

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 no guidance on when to use this tool instead of sibling tools like wordpress_get_media_analytics, wordpress_get_unused_media, or wordpress_upload_media. It does not mention alternatives or exclusions.

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