list_lists_trending

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful pagination behavior (defaults, clamping) and watchnow value semantics, which go beyond the schema. However, it doesn't describe response shape or any rate-limit/auth context, so it's adequate but not rich.

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 mostly a parameter list with some useful detail, but it's repetitive ('Query parameter' repeated 9 times) and not front-loaded with a clear summary. The watchnow block is verbose and could be condensed. It's structured but not tight.

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?

Given 13 optional parameters, an output schema, and read-only annotations, the description covers pagination and watchnow semantics but leaves most filter parameters undefined. For a simple trending-lists endpoint this is borderline adequate, but the lack of any guidance on filter formats or response contents is a clear gap.

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%, so the description must compensate. It does explain 'limit' pagination behavior and enumerates watchnow options, which is valuable. But most parameters (genres, subgenres, years, ratings, start_date, end_date, runtimes, countries, certifications) are just labeled 'Query parameter' with no format, allowed values, or semantics — leaving the agent to guess.

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 says 'Get trending lists' and includes the endpoint path, which clearly identifies the resource and action. However, it doesn't distinguish this from the sibling 'list_lists_popular' or 'get_lists_trending_by_type' — an agent could confuse which trending-lists variant to use. The verb 'Get' plus resource is clear, but sibling differentiation is absent.

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 provides no guidance on when to use this tool versus alternatives like list_lists_popular or get_lists_trending_by_type. It only lists parameters and the endpoint. There is no context about typical use cases, exclusions, or when a sibling would be more appropriate.

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