list-generated-files

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

No annotations are provided, so the description must carry the behavioral burden. It usefully discloses the backing endpoint as `GET /api/v1/files/generated`, implying a read operation, but it does not describe permissions, pagination behavior, ordering, or response shape.

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 front-loaded, compact, and wastes no sentences. The core purpose appears first, followed by the sibling distinction and implementation details.

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?

For a simple list tool this is minimally adequate, but there is no output schema and no annotations, so the description should do more to explain return behavior or pagination. Parameter documentation is also incomplete for `page` and `page_size`.

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 low at 33%, and the description only hints at the media-type filter by mentioning image/video/audio. It does not explain `page` or `page_size` semantics beyond what the schema's defaults and bounds show.

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 verb and resource: list files this account has generated, with supported media types. It explicitly distinguishes this from `list-uploaded-files`, so an agent can route correctly without opening either schema.

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?

It clearly positions the tool against `list-uploaded-files`, which is the key nearby alternative. However, it does not spell out when-not conditions or other usage boundaries, such as whether generation jobs must be complete before files appear.

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