seerr_get_blocklist

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

The readOnlyHint annotation declares the operation as read-only, and the description's 'get' verb aligns with that. However, the description adds no behavioral context beyond the annotation, such as behavior on missing entries, error conditions, or scope of results. It merely restates the tool's basic function.

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 a single short phrase, making it economical, but it is under-specified. It lacks structure and detail, so while there is no wasted text, the sentence does not earn its place by being informative.

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?

The tool's interface is simple, but the description fails to provide essential context: whether it returns a single blocklist item or a list, how it differs from listing the blocklist, and the role of the parameters. The existence of an output schema covers return values, but the description remains incomplete for selection and invocation.

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 description must compensate by explaining the parameters, but it does not. It offers no clarification of what tmdb_id and media_type mean or what values are acceptable, leaving the agent to guess based on the tool name and schema types.

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 media from blocklist' specifies a clear verb (get) and resource (media), and the parameters suggest it retrieves a specific entry. However, it does not explicitly distinguish itself from seerr_list_blocklist, which also deals with blocklist data, and lacks mention that tmdb_id and media_type identify a unique entry.

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 like seerr_list_blocklist or seerr_create_blocklist. No context, examples, or exclusions are provided, leaving the agent to infer the appropriate usage scenario.

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