list_series

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 description doesn't need to cover safety. But it adds no behavioral context beyond the HTTP endpoint and the parameter names. It does not disclose filtering behavior, response format, or any constraints beyond what annotations already imply.

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 very short and front-loaded with the purpose. However, it is under-specified rather than appropriately concise; it omits necessary semantic detail. The structure is acceptable but the content is too sparse to be effective.

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 tool with an output schema, the description might be adequate in isolation, but the context includes numerous sibling list/get tools and ambiguous parameters. The lack of usage guidance and parameter semantics makes the description incomplete for an agent deciding whether and how to invoke this tool.

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 compensate. It merely lists 'tvdb_id' and 'include_season_images' as 'Query parameter' with no explanation of their meaning or effect. This adds no value beyond the schema's types and titles, leaving the agent to guess what these parameters control.

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 specific verb and resource: 'Read Series.' It clearly identifies the tool as a read operation on series. However, it does not differentiate from siblings like list_series_lookup or get_series_by_id, so the agent must infer the scope from the endpoint path.

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 about when to use this tool versus alternatives. It does not mention that it lists all series, nor any conditions for using the optional parameters. The agent is left without context for selection among many list_* and get_* siblings.

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