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

Annotations already cover safety (readOnly, idempotent, non-destructive, open-world), yet the description adds substantial behavioral context beyond them: 1-hour caching with <5ms hits, a $0.01 per-call price, 5 free calls per agent_id, and critically that after quota exhaustion it returns a payment-required quote rather than a fatal error, plus the retry flow. This is exactly the kind of undisclosed-by-annotations detail that prevents agent failure loops.

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?

Front-loads purpose, then usage, then parameter interactions using clear labeled sections, so an agent can scan it quickly. It is slightly over-long with some redundancy (pricing stated as '$0.01 per call' and again in the 'Pricing:' clause) and payment mechanics that verge on marketing copy, but no sentence is wholly wasted.

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, return format needn't be restated, and the description covers the remaining gaps: cost, quota, caching, auth requirements, failure mode, and retry procedure. Nothing an agent needs to invoke this correctly is missing.

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 interaction semantics not present in the schema: omit agent_id and tx_hash during free trial calls, or supply agent_id (agd_pass_...) / tx_hash for paid execution. It clarifies the mutually-alternative relationship between the two optional auth params, which the schema only describes individually.

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 and resource ('Executes live Google News RSS + HackerNews Algolia search queries'), names the output quality ('clean, token-pruned results'), and implicitly distinguishes itself from the sibling get_agent_wallet_status by scoping it to search 'serp-extract' analysis. An agent can tell what this does without opening the schema.

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?

Contains explicit WHEN TO USE and WHEN NOT TO USE sections, names the alternative sibling for quota checks, and states the exclusion ('unrelated domains or binary media'). Routing is fully specified rather than inferred.

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