list_sync_collection_shows

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the description adds little behavioral context beyond the endpoint. It does not disclose pagination, filtering semantics, auth needs, or response characteristics, and 'Query parameter' is not a behavioral disclosure.

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 text is short, front-loaded, and well-structured with the endpoint followed by Args. It is genuinely concise, though the parameter descriptions are too sparse to be fully informative.

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 sits in a large sibling cluster and has two optional parameters that are not explained well enough to use correctly. With no usage context and no parameter value guidance, the definition is not complete for an agent, even though an output schema exists.

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 must compensate for the undocumented parameters. It only restates 'extended' as generic extra info and labels 'available_on' as a query parameter without giving allowed values or formats, which is insufficient for correct invocation.

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 uses a concrete verb and resource ('Get show collection') and gives the exact endpoint. It is clear at a glance, though it does not explicitly differentiate this from sibling collection tools like list_sync_collection_movies or list_sync_collection_minimal_shows.

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 call this tool versus alternatives. The sibling list contains several closely related sync-collection endpoints, and the description offers no context, exclusions, or prerequisites to help an agent choose between them.

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