list_sync_collection_media

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

Annotations already declare readOnlyHint=true and idempotentHint=true, but the description adds valuable behavioral details: pagination defaults (low default limit of 10), capping at endpoint maximum (250), and clamping rather than rejection. This goes beyond the annotations to inform the agent about response size behavior.

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 structured with the endpoint first, then a clean bullet-style list of parameters. It is concise and front-loaded with the purpose, keeping each parameter explanation short. No redundancy.

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?

This is a list tool with four parameters and many sibling tools. The description fails to clarify that this returns all media types (vs. type-specific siblings) or whether it includes episodes etc. It also doesn't mention the output schema's structure or any filters beyond the vague available_on. The agent could easily confuse it with list_sync_collection_movies or list_sync_collection_episodes.

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 explain parameters. It does explain 'page' and 'limit' clearly, and gives a vague 'Extended information' for extended. However, 'available_on' is merely described as 'Query parameter.' which adds no meaning beyond its name. Thus partial coverage with one unhelpful description.

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 'Get media collection' which is a verb+resource, but 'media collection' is vague and doesn't specify that it covers all media types (movies, shows, episodes) or how it differs from siblings like list_sync_collection_movies. It is not a tautology but lacks precision.

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 this tool versus the many type-specific siblings (list_sync_collection_movies, list_sync_collection_shows, etc.). The description does not mention alternatives or exclusions, leaving the agent to infer usage.

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