Liste WordPress Medien

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that it retrieves a list, omitting details about pagination defaults, response structure, potential performance implications, or any filtering behavior. This is minimal and insufficient for a tool with three optional parameters.

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 fluff, which is concise. However, it is under-specified to the point of being unhelpful; each word earns its place but the place is too small. A slightly longer description could add valuable context without losing conciseness.

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 tool is a simple list operation, but the description lacks any mention of return format, filtering capabilities, pagination, or relation to sibling media tools. Given no annotations and 0% schema coverage, the description is the only source of context and it provides almost none. The output schema exists but is not enough to compensate for the missing narrative.

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 0%, meaning no parameter descriptions exist in the schema. The description fails to explain the meaning of 'search', 'per_page', or 'media_type', leaving the agent to guess from the parameter names. This is a critical gap for correct invocation.

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 specific action ('Holt eine Liste' = 'Gets a list') on a clear resource ('aller Mediendateien' = 'all media files'), making the core purpose obvious. It does not explicitly differentiate from siblings like wp_get_media, but the singular/plural distinction plus the verb make 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?

The description provides no guidance on when to use this tool versus alternatives such as wp_get_media, image_list_sizes, or image_find_unused. There is no mention of prerequisites, filter use cases, or when not to use it, leaving the agent to infer usage from the name alone.

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