List video SKUs and prices

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

With no annotations, the description carries the behavioral burden and does well: it discloses that the data is live, prices are in USD, the call is free, and covers both fixed and custom endpoint variants. It stops short of explicitly confirming read-only/no side effects, but 'live catalog' strongly implies a non-mutating lookup.

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 compact sentences front-load the core purpose ('live catalog... with current USD prices') and then pack precise pricing detail and endpoint categories without filler. Every clause earns its place.

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 zero-parameter listing tool with no output schema, the description is complete: it tells the agent what the call returns, how current it is, that it is free, and what pricing/customization variants exist. No additional information is needed to invoke it correctly.

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?

The input schema has zero parameters, so the 0-param baseline of 4 applies. The description adds useful semantic context about what the no-argument call returns (pricing catalog) even though there are no parameters to document.

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 title and description together define a specific resource: a live catalog of pay-per-call video generation endpoints with current USD prices. It clearly distinguishes this listing tool from siblings like quote_price and generate_video, which handle pricing quotes and generation rather than catalog enumeration.

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 this is the tool to call for checking current catalog prices (it explicitly notes the call is free), but it does not state when to prefer it over alternatives like quote_price. The fixed-price vs. custom-endpoint distinction hints at routing, but no explicit when/when-not guidance is given.

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