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

Adds substantial context beyond annotations: it spends paid model usage, applies dedupe against published articles, persists results, suppresses raw source errors, and caps returned ideas at five. These are behavioral facts not derivable from the annotations (which only say readOnly=false, destructive=true, openWorld=true, idempotent=false).

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?

A single dense sentence plus a short imperative sentence; it is front-loaded with the core action and keeps every clause meaningful. Slightly long but well-earned given the multi-step behavior described.

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?

Covers the full pipeline, side effects (persistence, paid usage), output shape (aggregate counts, max five ideas), and error suppression. An output schema exists so return format need not be re-explained. Given the destructive+non-idempotent+open-world annotations and 7 params, this is largely complete, though it could clarify irreversibility or auth requirements.

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 100%, so parameters are fully documented in the schema (defaults, ranges, nested sources object). The description adds no parameter syntax or meaning beyond what the schema already provides, so baseline 3 is appropriate.

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 concrete multi-step pipeline (fetch, score, dedupe, persist) with a specific resource (topic ideas). Clearly distinguishable from list_topic_ideas (read-only listing) and set_topic_idea_status, which the name and description implicitly separate.

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?

Tells the agent to 'confirm sources and limits first,' which is a usable precondition. However it doesn't name alternatives (e.g., list_topic_ideas vs this refresh) or state when-not-to-use, so it falls short of the explicit routing that earns a 5.

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