get_discover_tv_network_by_network_id

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds no behavioral context beyond the HTTP method and parameter locations—no mention of pagination behavior, language handling, or response characteristics. It does not contradict 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 brief and organized: a one-line purpose, the endpoint URL, and a simple args list. No filler text. The args list is somewhat redundant with the schema but is still clear.

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 read-only discovery endpoint with three parameters and an output schema, the description covers the basic calling contract. It lacks a note on when to use it relative to sibling discovery tools and gives no extra detail about optional parameters, but the output schema exists to fill return-value gaps.

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 needed to compensate. It only restates parameter names and identifies path vs query parameters, but the endpoint already shows {networkId} in the path, and page/language are self-explanatory names with no added semantics, formats, or behavior.

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 a clear action ('Discover TV shows') and the resource modifier ('by network'), with the endpoint path confirming the resource. This distinguishes it from sibling discovery tools like get_discover_tv_genre_by_genre_id or get_discover_tv_language_by_language.

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 explicit guidance on when to use this tool versus alternatives; the only clue is the descriptive name and purpose line, which implies use when TV shows for a specific network are needed. Sibling alternatives such as get_network_by_network_id are not mentioned.

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