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

Annotations declare readOnlyHint=true and openWorldHint=true, and the description enriches these with genuinely useful behavior: the intentional, non-obvious sort ('a lower significance score can rank above a higher one, and that ordering is intentional; do not re-sort'), the concept of a maintained summary with source count, and cursor-based pagination. No contradiction with annotations found.

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 well-organized paragraph that front-loads the core behavior and ends with formatting guidance. Every sentence earns its place, though the enum examples for window and category do get re-stated relative to the schema, creating slight redundancy.

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 tool with no output schema, the description skillfully covers the key return semantics: row identity (situation as storyline with summary and source count), the cursor for pagination, and that URLs should be cited. It is complete enough for an agent to use the tool end-to-end without needing the response format spelled out.

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 the baseline is 3. The description adds meaningful context beyond the schema: how the ranking should be treated on the client side, the workflow implication of the cursor ('When there are more, the result ends with a cursor to page further'), and that the sort must be preserved verbatim. This justifies a point above the baseline.

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 immediately states the verb and resource ('List the situations developing right now') and gives a precise account of the ranking blend (significance, outlet count, recency), plus a crisp definition of what a 'situation' is. It stops short of a 5 because sibling differentiation is handled through usage hints ('when there is no specific topic yet') rather than explicitly contrasting with a sibling like search_situations.

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?

The description gives an explicit trigger ('what is going on in the world' / 'what is happening in <category>'), specifies when NOT to use it ('when there is no specific topic yet'), and chains the next step ('then open any result with get_situation_timeline'). It could be a 5 only if it explicitly named a search/topic sibling for the alternative case.

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