deaths_on_this_day

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

No annotations are provided, so the description carries the full burden. It adds useful behavioral context: the date is fixed to today's date in UTC, results are 'notable deaths', and the source is Wikipedia's On This Day feed. This clearly signals a read-only retrieval operation, though it does not describe return structure or pagination beyond that.

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 with no filler: the first front-loads the core action and scope, the second adds use cases and sibling relationships. Every sentence earns its place.

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 two-parameter read-only feed tool, the description is nearly complete: it names the source, scope, timezone, use cases, and sibling tools. Since there is no output schema, a brief note on the returned shape would have made it fully complete, but this is a minor gap.

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%, and the schema already fully documents 'lang' (with enum) and 'count' (default 5, max 10). The description adds no additional parameter-specific meaning, so baseline 3 is appropriate.

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 ('Get notable deaths... from Wikipedia's On This Day feed') and distinguishes itself as the 'deaths-only companion to on_this_day' which returns events. An agent can immediately tell what this tool does and how it differs from its closest sibling.

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?

Explicitly gives concrete use cases ('in memoriam' content hooks, obituary-style social posts, newsletter intros) and names complementary siblings (on_this_day, featured_article) for building a full digest. It also clarifies the boundary: deaths only, versus events from on_this_day.

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