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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so safety is covered. The description adds the useful cost signal ("1 credit"), but says nothing about result volume, pagination depth, freshness defaults, or how the engine fallback behaves at runtime — all relevant for a 12-param tool.

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 short sentences, front-loaded with the action and resource, with the credit cost isolated so it can be scanned independently. No filler or restatement of the tool name.

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 12 parameters and no output schema, the description leaves the agent guessing at the shape of results (titles, sources, dates, URLs) and whether paging is meaningful given the page maximum of 10. The schema carries parameter meaning well, so this is adequate but not complete.

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 92%, so nearly every parameter (including the domain include/boost/exclude semantics and the engine fallback list) is already documented in the schema. The description adds no parameter guidance beyond the schema, which is the correct baseline of 3 when coverage is this high.

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 ("Search Google News") and scopes it to recent articles, which distinguishes it from the general `search` sibling by name. It stops short of explicitly contrasting itself with `search`, `scholar`, or `webpage`, so the agent has to infer the boundary.

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?

No guidance on when to pick this over the many sibling search tools (search, scholar, images, shopping, videos), and no note on when a news-specific search is appropriate versus a general web search. The only added context is cost ("1 credit"), which is pricing, not usage selection.

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