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

Annotations already declare destructiveHint=true and idempotentHint=true, so the bar is lower. The description adds real context beyond them: the operation replaces (not appends to) existing lists, `clear: true` wipes all sources entirely, and feeds must be public HTTPS. It does not detail auth/permission requirements.

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?

Three tight sentences with the replacement behavior front-loaded, followed by the prerequisite and the parameter summary. No filler and no repetition of the schema.

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 an output schema present and full annotation coverage, the description needn't explain return values. It covers the mutation semantics, the clear escape hatch, the prerequisite, and the downstream dependency, which is everything an agent needs to call it correctly.

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 coverage is 100% so the baseline is 3, but the description adds combination semantics the schema does not: you pass `reddit` and/or `rss`, or `clear: true` to wipe everything. This clarifies how the four parameters interact rather than merely restating them.

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?

States a specific verb (Replace/Set) and resource (Reddit subreddits and/or public HTTPS RSS feeds for topic research), and names the downstream sibling refresh_topic_ideas. An agent can immediately distinguish this from refresh_topic_ideas or list_topic_ideas.

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?

Provides a clear prerequisite ('Confirm the complete replacement lists before calling') and clarifies the downstream relationship to refresh_topic_ideas. It does not explicitly state when-not to use it versus alternatives like list_topic_ideas, so it stops short of the top score.

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