Get sync snapshot

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. Beyond that the description adds nothing: no mention of pagination via `cursor`/`limit`, no explanation that `since` enables incremental sync, and no statement about result size or ordering. For a bulk-read tool, the incremental/pagination behavior is the most important thing to disclose.

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?

One short sentence, front-loaded with the verb and the payload, with no filler. It is efficient, though brevity here comes at the cost of the missing behavioral detail noted elsewhere.

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 six parameters, no output schema, and pagination plus a timestamp-based incremental filter, the description should say how paging and delta-sync work and roughly what a response contains. It covers only the kind enumeration, leaving the agent to discover pagination behavior from the schema alone.

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 83%, so the baseline is 3. The description's kind list is essentially a restatement of the `kind` enum and adds no syntax, default, or format detail for `since`, `cursor`, `limit`, or `tmdb` beyond what the schema already says.

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?

States a clear verb ('Get') and enumerates the five record kinds it returns, so an agent can tell it is a bulk snapshot reader rather than a single-item lookup. It loses a point because it never distinguishes itself from sibling readers that overlap heavily (get_ratings, get_watchlist, get_user_stats), and the title's 'sync snapshot' framing is not developed in the description.

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?

Usage is only implied: the enumerated kinds map to the required `kind` parameter, so an agent can infer what each call retrieves. There is no explicit when-to-use/when-not-to-use and no routing to alternatives such as get_ratings or get_watchlist, which return overlapping data.

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