list_sync_collection_movies

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context about pagination: low default limits near 10, endpoint maximums near 250, and clamping of higher limit values rather than rejection. This goes beyond the structured 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 appropriately compact and front-loads the main purpose. The Args section is neatly structured, and the pagination note, while somewhat boilerplate, is concise and relevant. No sentences are wasted, though the endpoint line could arguably be merged with the first sentence.

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 description covers the core operation and pagination behavior, and the output schema plus read-only annotations reduce what is missing. However, it does not explain valid values for extended or available_on, and it lacks any mention of authentication or relationship to sibling sync-collection endpoints. This is adequate for a simple GET list but has clear gaps.

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 schema has 0% description coverage, so the description must compensate. It meaningfully explains page and limit, including default/cap behavior. However, 'extended: Extended information to include in the response' is vague, and 'available_on: Query parameter' is essentially a tautology that adds no semantic value. Half the parameters remain opaque.

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 states the verb 'Get' and the resource 'movie collection', and the endpoint GET /sync/collection/movies makes the scope concrete. It is distinguishable from sibling tools like list_sync_collection_shows or list_sync_collection_minimal_movies primarily by the explicit movie-collection resource, though it does not explain what 'collection' means in this sync context.

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 about when to use this tool versus alternatives such as list_sync_collection_media, list_sync_collection_minimal_movies, or get_sync_collection_by_type. The intended use is only implied by the name and endpoint, with no exclusions, prerequisites, or comparison to related sync collection tools.

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