list_movie

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds little beyond the HTTP method and parameter names; it does not explain result set semantics, filtering effects, or other behavioral details, but it does not contradict the 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 short, front-loaded with 'Read Movie,' and structured with the endpoint and argument list. It contains minimal fluff, though the 'Args' section is mostly redundant with the schema.

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?

Even with an output schema and safety annotations, the description lacks essential context about how the query parameters behave and when this tool should be selected over similar movie-related list/lookup tools. An agent could call it, but might misuse filters or choose the wrong sibling.

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%, and the description only repeats each parameter name followed by 'Query parameter.' It provides no actual meaning for tmdb_id, exclude_local_covers, or language_id beyond what the schema already shows with types and defaults.

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 identifies the operation as 'Read Movie' and gives the GET /api/v3/movie endpoint, which clearly indicates a read/list action on the movie collection. It is specific enough to distinguish from create/update/delete tools, though it does not explicitly differentiate itself from similar list/get movie 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?

There is no guidance about when to use this tool versus alternatives such as list_movie_lookup or get_movie_by_id. The description simply lists the endpoint and arguments, leaving the agent to infer the appropriate use case.

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