List renders

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

No annotations are provided, so the description carries full burden. It discloses ordering (newest first) and optional type filter, but does not mention whether the operation is read-only, what happens with deleted renders, or any rate limits. The behavior is partially transparent.

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?

Two sentences, no unnecessary words. Front-loaded with the main action and ordering. Every sentence adds value.

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?

No output schema. The description lacks details on response format, pagination behavior (beyond knowing page/limit exist), or any edge cases. For a list tool, it could be more complete but is minimally adequate.

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 67% (page and limit have descriptions, type only enum). The description adds that type can filter by video/image, but this is already in the schema's enum. No new meaning is added beyond what the schema provides, so baseline 3.

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 tool lists render jobs for the account, sorted newest first, with an optional type filter. It uses specific verb and resource, and because sibling tools include list_bulk_renders, this description distinguishes itself by focusing on standard renders vs. bulk renders.

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 gives the core purpose and the optional filter but does not provide guidance on when to use this tool vs. alternatives like get_render, list_bulk_renders, or how to handle pagination. No explicit when-not-to-use or alternative naming.

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