seerr_get_media_watch_data

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

The readOnlyHint annotation is present and consistent with the 'Get' verb, so there is no contradiction. However, the description adds no behavioral context beyond what the annotation already provides—there is no mention of what data is actually returned, whether it is scoped to a specific user, or any limitations. The output schema may cover return structure, but the description contributes little.

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?

At three words, it is extremely short, but this is under-specification rather than effective conciseness. The description omits critical information about the tool's purpose and parameter, making it similar to the 'Process' example in calibration.

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?

Given the tool is a simple getter with one parameter and an output schema, the description is not required to be lengthy, but it fails to convey what 'watch data' means or how this tool fits relative to the numerous sibling tools. The lack of context leaves the agent unsure whether this is the right tool for a given query.

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 one required parameter, media_id, with no description (schema description coverage is 0%). The description does not explain what media_id should be, its format, or how it relates to 'watch data.' It adds zero meaning beyond the parameter name itself, which is insufficient for an agent to construct correct invocations.

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 'Get watch data' states a verb and an object, but it is vague: it does not specify what 'watch data' includes (e.g., ratings, history, status) or for which media type. It also does not distinguish it from sibling tools like seerr_get_user_watch_data, which could easily be confused for the same purpose.

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 usage guidance is provided. The description does not mention when to use this tool, what alternatives exist, or how it differs from seerr_get_user_watch_data, seerr_get_user_watchlist, or other media-related getters. There is no context to help an agent choose between tools.

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