list_movies_blacklist

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 safety profile is covered. The description adds the HTTP endpoint but does not disclose pagination behavior, default limits, or any side effects, though these are minor for a simple read operation.

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 short and front-loaded with the purpose, followed by the endpoint and arguments. The Args section largely repeats schema information but does not create significant bloat.

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?

With only two optional parameters, an output schema, and safety-oriented annotations, the description is close to sufficient. It is incomplete mainly because it does not clarify pagination semantics or contrast with sibling list tools, but no major context is missing for a basic read-only listing.

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 carry parameter meaning. It only says 'start: Paging start integer' and 'length: Paging length integer', which adds minimal value beyond the property names and does not explain whether start is an offset, how length is bounded, or what happens when parameters are null.

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 names a specific verb and resource: it lists blacklisted movie subtitles, making the core purpose understandable. However, it does not differentiate itself from sibling tools like list_episodes_blacklist or list_movies, so it relies partly on the tool name for distinction.

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 about when to use this tool versus alternatives such as list_movies or list_movies_wanted. The description only provides the endpoint and paging arguments, leaving the selection context entirely to the agent's inference.

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