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

Beyond the readOnly/openWorld annotations, the description discloses useful traits: the list size (~10), that it is market-invariant ('the same in every market'), that no input is required, and what enrichment adds. It says nothing about rate limits, caching, or how fresh 'right now' actually is.

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 the core behavior and followed by the usage cue. The phrase 'resolved to their events with enriched' is grammatically awkward and slightly obscures the flag's role, but there is no filler.

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?

An output schema exists and the single optional parameter is fully documented, so the description covers what remains: cardinality, no required input, and market-invariance. An agent can call it confidently; only the freshness/timing of the trending snapshot is left unstated.

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 enriched flag is already documented as resolving terms to event/competition/entity type, so the schema carries the weight. The description's clause 'optionally resolved to their events with enriched' restates the same behavior rather than adding new semantics.

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 concrete verb and resource — the trending terms shown in the FanDuel Sportsbook search box — with expected cardinality (about ten) and entity types (players, teams, clubs). It is clearly a snapshot read rather than a query endpoint, but it never names the adjacent siblings (autocomplete, search, search_tabs) it should be distinguished from.

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?

'Use it to see what bettors are looking at right now' gives a clear situational trigger and the note that it requires no input lowers the call barrier. There are no explicit exclusions or pointers to alternatives for query-driven lookups, so it stops short of a 5.

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