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

With no annotations, the description carries the full behavioral burden. It does disclose two useful traits — the feed is real-time ('right now') and ordered newest first, and each entry pairs a query with its answering page — but it says nothing about freshness window, refresh/caching behavior, default result count, or whether results can be empty, which matters for an unannotated read 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?

A single short sentence with no filler, front-loading what the tool returns. The subordinate clause 'and the page that answers each' is slightly awkward but genuinely informative, so almost nothing is 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?

For a simple read tool with one optional integer and no output schema, the definition covers the broad shape of the result (queries plus answering pages, newest first). It still leaves the default limit, the freshness semantics, and the actual per-item field structure unaddressed, which is the main gap given no output schema exists.

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 0% and the description never mentions the single 'limit' parameter, its default, or how the maximum of 50 interacts with the newest-first ordering. The only meaning conveyed is ordering ('newest first'), leaving the one parameter to be inferred entirely from the raw 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?

The description names the resource concretely: what the World is looking up right now, paired with the page that answers each, returned newest first. That is specific enough to distinguish it from list_sites (a site inventory) and suggest (query suggestions), though the phrasing is more evocative than operational and states no explicit verb like 'list' or 'get'.

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?

There is no when-to-use guidance and no mention of any alternative. The 'right now' framing implies a real-time/trending use case, but the agent must infer that on its own, and nothing says when a static listing or a suggestion tool would be preferable.

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