list_discover_movies

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

Annotations already cover read-only, idempotent, non-destructive behavior. The description adds only the URL and a parameter name list, with no mention of default sort, pagination behavior, date formats, or filter value semantics. It does not contradict the annotations but provides little beyond them.

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 useful content is a single phrase plus endpoint, but eighteen lines are spent listing parameter names that already exist in the schema. The repetitive 'Query parameter' suffix makes the structure bloated and redundant rather than concise.

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 16 optional filter parameters, no parameter descriptions, and no examples of valid values or combinations, an agent cannot reliably construct a correct request. The output schema covers return values, but the missing parameter semantics leave an unacceptable gap for a tool this complex.

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 carries the full burden of explaining parameters. It only repeats each parameter name followed by 'Query parameter', offering no meaning for fields like sort_by, primary_release_date_gte, or watch_providers. This is a pure restatement of the schema with zero added semantic value.

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 identifies a read operation for movies via 'Discover movies' and the explicit GET endpoint. It names the resource and the action, but does not distinguish it from siblings like list_discover_tv or list_discover_movies_upcoming, so it misses the top level of clarity.

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 on when to use this tool instead of related discovery endpoints, nor any conditions or exclusions. An agent is given no context for selecting this over list_discover_trending or list_discover_movies_upcoming.

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