dino_fact

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

With no annotations, the description carries the full burden. It usefully discloses the fallback behavior (a missing species silently returns a random dino) and that facts originate from Wikipedia, but it omits any note on rate limits, network dependence, or the shape of the returned fact.

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?

Three sentences, front-loaded with purpose and then split cleanly between the targeted and random modes. Minor redundancy: the random-dino case is stated twice (no-arguments and fallback).

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 two-parameter, annotation-free tool with no output schema, the description covers purpose, both invocation modes, and fallback behavior. The only meaningful gap is the absence of any indication of what the returned fact 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 100%, so both the 'species' and 'lang' parameters are already documented (including the empty-string-for-random convention). The description restates the species semantics but does not explain the 'lang' enum's effect on output, so the baseline of 3 applies.

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 uses a specific verb+resource combination ('Get a Did You Know style fact about dinosaurs or prehistoric life'), which is concrete and distinguishable from the generic sibling 'did_you_know' by domain. It stops short of explicitly naming the sibling to route away from, so it is clear but not maximally differentiating.

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?

It clearly states the two invocation modes: pass a species name for a targeted fact, or call with no arguments for a random dino. This is explicit context for how to use the tool, though it offers no exclusion guidance relative to sibling fact/article tools.

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