APIbase

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

Annotations cover safety profile (readOnly, idempotent, non-destructive). The description adds valuable behavioral context by specifying the similarity algorithm factors (genres, themes, cast) and data source (TMDB), which helps set expectations for result quality. Does not mention pagination behavior or rate limits.

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?

Single, tightly constructed sentence with zero waste. Front-loaded with the action ('Get'), immediately followed by the resource and key parameter context, ending with similarity criteria and source attribution. 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?

Appropriate for a simple read-only lookup tool with 100% schema coverage and comprehensive annotations. The description successfully conveys the core purpose without needing to detail return values (implied by 'recommendations' and tool name). Complete enough given the low complexity and rich structured metadata.

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 100%, establishing a baseline of 3. The description references 'movie ID' which maps to the required 'id' parameter, reinforcing its purpose. No additional semantic detail provided for 'language' or 'page' parameters beyond what the schema already documents.

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?

Clear verb+resource combination ('Get movie recommendations') and specifies the similarity basis ('similar genres, themes, cast'). However, it does not explicitly differentiate from sibling tools like 'tmdb.movies.discover' or 'tmdb.movies.search', which could help the agent choose between recommendation approaches.

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?

Provides implied usage context by stating the tool works 'based on a movie ID', suggesting a prerequisite ID from other TMDB tools. However, it lacks explicit 'when to use' guidance or contrast with alternatives like the discover endpoint.

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