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

Annotations cover the safety profile (readOnlyHint=true, openWorldHint=false), so the bar is lower, and the description still adds real behavioral context: result ordering ('best first'), the corpus boundary (last year of daily and weekly issues), and the shape of each result. With no output schema, this return-shape disclosure is doing useful work.

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 sentences, front-loaded with scope and return shape, with no padding. The final syntax clause is slightly garbled ('or.') but does not meaningfully impede use.

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?

No output schema exists, and the description compensates by naming the returned fields and ordering, plus the corpus time window. The enum-backed `group` values and `limit` default are left to the schema, which documents them adequately.

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 coverage is 100%, so baseline would be 3; the description earns above that by documenting the query grammar (words, quoted phrases, -word negation), which the schema only describes as 'what to look for'. The `since` bound is also implied by the 'last year' corpus statement.

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 the stories in the Observatory's published issues') plus the coverage window (daily/weekly, last year), which is enough to separate it from search_book and latest_issues by resource. It never names a sibling explicitly, so the differentiation is implicit rather than stated.

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 scope ('published issues, last year') implies when the tool applies, and the query-syntax note gives invocation guidance. There is no explicit when-to-use/when-not or pointer to an alternative tool such as search_book for non-issue content.

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