list_discover_trending

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

Annotations declare readOnlyHint=true and idempotentHint=true, which the description aligns with. However, the description adds little beyond the endpoint and basic parameters; it does not mention pagination limits or default language behavior.

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?

Extremely concise, with the purpose stated in one line, the endpoint shown, and parameters listed in minimal lines. Zero fluff, information dense.

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 a simple list operation with optional parameters and an output schema, the description is largely complete. It lacks detailed parameter semantics but that's a minor gap for this simplicity.

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% and parameters are only documented as 'Query parameter' in the description, repeating the schema's title/type. This provides minimal insight into accepted formats or defaults.

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 'Trending movies and TV' and includes the endpoint 'GET /api/v1/discover/trending', clearly indicating a read operation. It is distinct from siblings like list_discover_movies or list_discover_tv by focusing on trending content.

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?

Implied as a general-purpose list for trending media, with no explicit when-to-use or when-not-to-use guidance. Sibling names suggest alternatives but no specific comparisons are made.

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