Get movie cast & crew

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

Annotations already indicate a safe read operation (readOnlyHint true) and openWorldHint true. The description adds valuable behavioral context: it lists 'top-billed' cast and 'headline crew' with examples (director, writers, etc.), implying it is not exhaustive. No contradiction 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?

The description is extremely concise: two sentences that cover purpose, usage, and context with zero superfluous information.

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?

Despite lacking an output schema, the description is sufficient for an agent to understand what the tool does and invoke it correctly. It could mention the output format (e.g., JSON arrays), but the name and context imply the structure.

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?

The parameter id is fully described in the schema (TMDB numeric id). The description adds that it comes from search_movies, but this is more about obtaining the parameter than its semantics. With 100% schema coverage, a score of 3 is appropriate as the description does not significantly enhance parameter understanding.

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 what the tool does: list top-billed cast and headline crew for a movie by TMDB id. It also specifies that the id comes from search_movies, which distinguishes it from sibling tools like get_tv_credits or get_person_credits.

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 tells when to use the tool (to get movie credits) and where to obtain the required id (search_movies). It does not explicitly exclude alternatives, but the context is clear enough for an agent to select appropriately.

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