get_shows_by_id_watching

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the read-only safety profile is covered. The description adds no behavioral nuance beyond the endpoint—nothing about time windows, pagination, or response semantics—so it contributes little beyond the 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 optimally concise: a one-line purpose, the endpoint, and a compact argument list. Every sentence carries information and the structure is easy to scan, with the main purpose front-loaded.

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?

For a simple two-parameter read operation with annotations and an output schema present, the baseline information is mostly adequate. However, it lacks usage context relative to the large sibling set and does not clarify the 'extended' parameter, leaving a notable gap for an agent deciding between similar watching endpoints.

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?

With 0% schema description coverage, the burden falls on the description. It adds minimal value: 'id: The id/slug of the resource' is helpful, but 'extended: Extended information to include in the response' is essentially a restatement of the parameter name and gives no concrete guidance about accepted values or what extended info is returned.

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 opens with a specific verb and resource: 'Get users watching right now,' backed by the explicit endpoint 'GET /shows/{id}/watching.' This makes clear it returns users currently watching a given show, and the endpoint distinguishes it from sibling tools like get_movies_by_id_watching, though it does not explicitly name them.

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 on when to use this tool versus alternatives such as get_users_by_id_watching or get_movies_by_id_watching. The description only states the endpoint and arguments, leaving the agent to infer the appropriate context from the resource path.

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