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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the closing "Safe read-only" adds little. However, the description does add real behavioral context beyond annotations: it explains the downstream effect that matching articles are filtered out of new item views and newspaper editions, which tells the agent why this list matters.

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?

Two compact sentences front-load the purpose before the filtering effect. The trailing "Safe read-only" is redundant with the annotations and could be dropped, but it does not obscure anything.

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 zero-parameter, non-destructive read tool with full annotation coverage, the description covers purpose and effect adequately. The only mild gap is that it never hints at what a keyword entry contains (e.g., the keyword text and whether it is active), which matters slightly since there is no output schema.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. No syntactic detail is needed or missing.

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?

Uses a specific verb and resource ("Lists all keyword filters") scoped to the current user, which cleanly separates it from the other list_* siblings (list_feeds, list_folders, list_items) that return different resources.

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?

Usage is implied rather than stated: an agent can infer it should call this when it needs to see what content is being suppressed, but there is no explicit when-to-use framing, no mention of prerequisites, and no note that no sibling tool covers muted keywords.

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