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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint), and the description still adds real behavior: the ~24h recency window and newest-first ordering, which the annotations cannot convey. It does not mention rate limits, upstream availability, or failure behavior for an open-world external feed, which keeps it from a 5.

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, zero filler, and the most decision-relevant fact (the ~24h recency window) is front-loaded.

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?

Annotations are rich and there is no output schema, so the description doesn't need to explain return values. But for a tool with an undocumented limit parameter and an external open-world data source, it leaves the agent guessing how many alerts come back and what a typical response looks like.

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 50%: city is documented in the schema itself, and the description's 'Optional Hebrew city filter' largely restates that. The limit parameter is undocumented in both the schema and the description (no indication that it caps the number of alerts returned), so the description does not compensate for the coverage gap; baseline 3.

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 a specific resource (Home Front Command alert history) and a concrete scope (~last 24h, newest first), so the agent knows exactly what it returns. It implicitly separates itself from the sibling oref_current_alerts via 'history' vs. 'current', but never names that sibling or states the contrast explicitly.

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 ~24h window implies when this tool is relevant and carries a weak implication that live alerts belong to oref_current_alerts. However, there is no explicit when-to-use/when-not statement and no alternative is named despite oref_current_alerts sitting right next to it in the tool list.

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