Get similar titles

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

Annotations already declare readOnlyHint=true and openWorldHint=true. Description adds significant behavioral context: noise from shared keywords, filtering out broad genre matches, misleading total_pages/total_results counts, and per-page results may be thin or empty. No contradictions with annotations.

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?

Description is front-loaded with purpose, but is somewhat verbose. However, every sentence adds value (contrast with recommendations, caveats about filtering and pagination). Could be slightly more concise, but the information density justifies the length.

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 complexity (filtering, misleading pagination counts, possibility of empty results) and presence of output schema, the description fully covers behavioral nuances and return value interpretation. It explains not to use total_pages/total_results for gauging similarity depth, which is critical. Very complete.

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% with all parameters described. Description adds minor context (e.g., 'Get the id from search_movies/search_tv' for id, pagination context for page), but does not significantly enhance parameter meaning beyond the schema. Baseline of 3 is appropriate given high coverage.

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?

Description clearly states the tool retrieves titles TMDB considers similar based on shared genres and keywords, and explicitly contrasts with get_movie_recommendations/get_tv_recommendations. It uses specific verb 'Get' and specifies resource 'titles similar to a given movie or TV show', distinguishing it from siblings.

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?

Explicitly advises to use recommendations first for thematically closer picks, and use this for genre/keyword-adjacent similarity. Also states prerequisite: 'Get the id from search_movies/search_tv.' Provides clear when-to-use and when-not-to-use guidance.

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