list_media

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

The description includes a helpful size hint (22 entries, safe for context window), which is a positive behavioral disclosure. However, it does not explain the effect of the per_page parameter or any pagination behavior, and no annotations are present to cover other traits.

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 extremely concise with two sentences, efficiently conveying purpose and a context hint. However, it could be slightly improved by including parameter info 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 description lacks critical information such as return format, pagination behavior, and the effect of the per_page parameter. There is no output schema, so the agent cannot anticipate the structure of the response.

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?

With 0% schema description coverage, the description must explain parameters but fails to mention the per_page parameter or its role in pagination. The agent receives no guidance on how to use this parameter.

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 verb 'List' and resource 'installation media' with scope 'all', providing a clear purpose. However, it does not explicitly distinguish from sibling get_media, though the verb 'list' vs 'get' implies a difference.

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?

No usage guidelines are provided. The description does not specify when to use this tool versus alternatives like get_media, nor does it offer any context on prerequisites or typical use cases.

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