APIbase

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

Annotations already declare read-only, idempotent, non-destructive behavior. The description adds valuable context beyond annotations: it identifies TMDB as the external data source and clarifies the scope includes three distinct entity types (movies, TV shows, people).

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?

Exemplary brevity: a single sentence packs the resource type, content variants, time granularity, and data source with zero redundancy. Every word earns its place and critical information is front-loaded.

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 the simple parameter structure (4 optional primitives, 100% schema coverage) and rich annotations, the description provides sufficient context. It appropriately omits return value details (no output schema exists) while conveying the essential API behavior.

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?

While the schema has 100% description coverage, the description adds semantic grounding by enumerating the concrete options ('movies, TV shows, or people' for type; 'daily or weekly' for window) that map to the schema enums, reinforcing the parameter purposes beyond technical specifications.

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 retrieves 'trending' content (movies, TV, people) with time granularity (daily/weekly) and identifies the TMDB source. The 'trending' keyword effectively distinguishes this from sibling tools like 'search' or 'discover', though it doesn't explicitly contrast with them.

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 usage by specifying the time windows ('daily or weekly') and content types available, guiding parameter selection. However, it lacks explicit guidance on when to choose this over 'tmdb.movies.discover' or 'tmdb.movies.search' for finding popular content.

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