seerr_create_blocklist

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

Annotations already indicate a write operation (readOnlyHint: false). The description adds 'WRITE: this modifies your Seerr instance,' reinforcing the side effect but providing no additional behavioral detail such as whether the modification is reversible or what specific data is changed. This adds marginal value beyond 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 front-loaded with the core action. The 'WRITE' warning is somewhat redundant given the annotations, but it is a single sentence and does not waste words.

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 tool with an opaque 'body' parameter and a write operation, the description is insufficiently informative. It does not explain the expected request payload, return value, or prerequisites, and there is no reference to related blocklist tools for context.

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?

The input schema has a single 'body' parameter with no description, and schema description coverage is 0%. The description does not mention the parameter at all, leaving the agent without any clue about required fields, structure, or examples for adding media to the blocklist.

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 clearly states the action ('Add media to blocklist') with a specific verb and resource. It distinguishes itself from the related sibling 'seerr_create_blocklist_collection' by focusing on media items rather than collection creation, though it doesn't explicitly name alternatives.

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 on when to use this tool versus alternatives like 'seerr_create_blocklist_collection', 'seerr_list_blocklist', or 'seerr_delete_blocklist'. The description only states what it does, not the context or exclusions.

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