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

Annotations already cover readOnly/idempotent/openWorld=false, so the safety profile is settled. The description adds value beyond that by naming the data source (Stake Engine Insights) and the shape of each entry (publisher, average bet). It omits only secondary behaviors like caching or tie-breaking.

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?

A single dense sentence with no filler; the ranking basis and returned fields are front-loaded, and nothing is repeated from the schema.

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, so return-value detail is not needed. However, with zero schema description coverage, the absence of any mention of limit behavior, default ordering metric, and how ties or 'all' range behave leaves gaps for a 3-parameter ranking tool.

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 0%, so the description must carry the parameters. It covers 'range' and 'category' (turnover vs. bets), but 'limit' is only hinted at by the word 'top' – the maximum of 25 and default of 10 are left entirely to the schema, and the default metric (bets) is not stated.

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?

Names a specific resource (Stake Engine slots) and states the ranking dimension explicitly: 'most played... by turnover or bet count over a range.' It also discloses the returned fields (publisher, average bet), which distinguishes it from stake_slot_lookup and stake_list_games without naming them.

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?

Usage is implied by 'most played... over a range' – the agent can infer this is for leaderboard/discovery queries – but there is no explicit when-to-use or when-not, and no guidance on choosing between stake_slot_lookup (details on a known slot) versus this ranking tool.

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