list_collection

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

Annotations already declare the read-only, idempotent, non-destructive behavior. The description adds the endpoint and the tmdb_id query-parameter scoping, which is useful, but it does not explain what happens when tmdb_id is omitted or whether pagination applies.

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 compact and front-loads the one-line summary before the endpoint and argument. There is no filler, though it borders on under-specification.

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?

The tool is simple, has an output schema, and safety behavior is covered by annotations, so the description is minimally usable. The main gap is that it never distinguishes this read path from get_collection_by_id or clarifies the behavior of the optional tmdb_id parameter.

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 needed to clarify the parameter, but it only labels tmdb_id as a query parameter. It does not describe how the ID selects the collection or how omitting it affects the response, adding minimal meaning beyond the schema.

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 names a specific verb ('Read') and resource ('Collection') and gives the concrete GET endpoint, making the core operation recognizable. It does not explicitly contrast with sibling get_collection_by_id, so it misses top-tier differentiation.

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?

No guidance is provided on when to use list_collection versus get_collection_by_id or update_collection. The description only states the endpoint and argument, leaving the agent to infer the correct selection.

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