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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true), so the burden is lower. The description still adds real context beyond them: the data source (Google News sitemap), the freshness guarantee, the note that the site has no RSS feed, and the exclusions of video, partner-content, and section pages. That is meaningful scope disclosure, though nothing is said about volume, pagination, or failure modes.

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 short sentences, front-loaded with the outcome and source, then the exclusions, then the routing advice. No filler and no repetition of the tool name or annotations.

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?

An output schema exists, so return values need not be described. For a zero-parameter, read-only feed the description covers what the tool returns, where it comes from, what it omits, and which sibling to use instead. Nothing an agent needs in order to call it 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?

The tool takes zero parameters, so there is no parameter semantics to explain, and a 4 baseline applies. Nothing in the description contradicts or misuses the empty schema.

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 ('Returns fresh Khaleej Times top stories') and names the exact source ('public Google News sitemap'), which no sibling tool in the news family exposes. It also distinguishes itself from khaleejtimes_headlines, so an agent can route correctly without opening either 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?

It explicitly routes the agent to khaleejtimes_headlines when section headlines are wanted, which gives a clear selection rule between the two Khaleej Times headline tools. It does not address the other siblings (khaleejtimes_article, khaleejtimes_sections), but the core alternative is named and conditioned.

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