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

Annotations already declare this is a non-read-only, idempotent, non-destructive operation. The description adds useful behavioral context beyond annotations: the exact Redis key family affected, the downstream effect of lists being re-read from MongoDB, and the meaning of the `flushed` response field.

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 three front-loaded sentences with no filler. The purpose, identifier requirement, and return-field meaning each appear directly and earn their place.

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 low-complexity cache-flush tool with no output schema, the description covers the essential operation, identifier selection, and return semantics. A minor gap remains around required-parameter behavior, since the schema marks both identifiers optional but the tool presumably needs one.

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 does clarify that `website_id` and `website_uuid` are alternative identifiers, but it does not explain edge cases such as what happens if neither or both are supplied, or whether one identifier form is preferred.

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: flushing the Redis SLAVE-LIST cache for a seliee_website. It specifies the scope tightly enough that an agent can distinguish it from broader website cache purges and other cache tools.

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?

It says to pass `website_id` or `website_uuid` and implies the operation is for forcing website lists to be re-read from MongoDB. However, it does not explicitly state when to use this rather than sibling cache-flush tools such as purge_website_cache_all or clear_page_cache.

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