Get similar titles

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

Annotations already convey read-only and open-world nature. The description adds context that the list is algorithmic and distinct from recommendations, providing behavioral nuance beyond annotations. 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?

Two concise sentences: the first states purpose and differentiation, the second provides a practical usage hint. Every sentence adds value without redundancy.

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?

With complete schema descriptions and annotations covering safety and openness, the description sufficiently explains the tool's function and how to use it. It lacks details on pagination or result format, but this is acceptable for a read-only list tool without an output schema.

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 clear descriptions for all parameters. The description mentions media_type and id indirectly but does not add new semantics or constraints beyond the schema, meeting the baseline.

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 it gets titles TMDB considers similar to a given movie or TV show, distinguishing it from get_movie_recommendations. It specifies the verb 'Get' and the resource 'similar titles', making the purpose unambiguous.

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 explicitly advises to obtain the id from search_movies/search_tv and notes that this is distinct from get_movie_recommendations, which provides clear context. However, it does not address when to use it versus other sibling tools like discover or trending, which slightly limits completeness.

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