show_medias

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

No annotations are provided, so the description bears full responsibility. It mentions pagination (a behavioral trait) but omits critical information such as authentication requirements, rate limits, side effects, or response format. The presence of an output schema partially mitigates this, but the description adds little beyond the schema.

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 concise sentence that conveys the core functionality. It is front-loaded with essential information and contains no extraneous words.

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 has a simple interface with three parameters and an output schema. The description covers pagination and optional filtering, which is sufficient for basic usage. While it does not differentiate deeply from siblings, the output schema fills in return value details.

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%, requiring the description to compensate. It adds that the 'kind' parameter accepts 'image' or 'video' values, which is helpful. However, 'limit' and 'offset' parameters are not elaborated upon; their meanings are inferred from pagination context but not explicitly defined.

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?

Description clearly states the verb 'show' and resource 'medias', specifies it is a paginated library, and mentions an optional kind filter. This distinguishes it from siblings like media_upload or show_generations.

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 implies usage for browsing the media library with optional filtering, but provides no explicit guidance on when to use this tool versus alternatives like show_generations or media_upload. No exclusions or prerequisites are mentioned.

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