get-movie-recommendations

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

No annotations exist, so the description carries full burden. Beyond mentioning the TMDB API, it discloses no behavioral traits such as data mutability, rate limits, error conditions, or return format. The agent cannot assess safety or side effects from this description.

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?

The description is a single sentence that is under-specified rather than appropriately concise. It fails to provide essential details that would justify its brevity (e.g., no parameter explanations, no usage context). Prefer a more informative but still concise structure.

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 3 parameters, no annotations, and no output schema, the description is critically incomplete. It does not explain return values, pagination (page parameter), language support, or what happens when no recommendations exist. The agent lacks sufficient information to use the tool correctly.

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%, so the description must explain parameters. It does not: only 'based on a specific movie' hints at movieId, but page and language are completely undocumented. No meaning is added beyond the schema's structural information.

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's function: getting movie recommendations based on a specific movie via the TMDB API. The verb 'Get' and resource 'movie recommendations' are specific. It distinguishes from siblings like 'search-movies' or 'get-movie-details' by focusing on recommendations, though it doesn't explicitly differentiate.

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 provides no guidance on when to use this tool versus alternatives (e.g., search-movies, discover-movies). There is no mention of prerequisites, context, or exclusions. The agent is left to infer usage from the tool name alone.

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