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

With no annotations, the description carries full burden. It discloses that only casinos with completed real-money deposit/withdrawal tests are ranked, and mentions factors (payout speed, KYC, support, license). This gives good insight into the tool's filtering and ranking logic, though it omits data freshness or update frequency.

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: purpose with criteria, usage examples, and an example call. Every sentence is essential and front-loaded. No redundancy or fluff.

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 list tool with one parameter and no output schema, the description covers purpose, ranking criteria, and usage context. It lacks details about output format (e.g., fields returned) or ordering (presumably descending by trust score), which would improve completeness.

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 0% (no parameter description in the schema). The description provides an example call with {'limit': 10}, implying the parameter controls result count, but does not explicitly define 'limit' or its behavior (e.g., maximum, default). This adds modest value beyond the schema's min/max/default constraints.

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 clearly states it ranks best crypto casinos by 'WagerX audit trust score' and lists specific criteria (payout speed, KYC, support, license). It distinguishes from sibling tools like 'list_casinos' (general list) and 'new_casinos' (recent additions) by focusing on a curated trust-based ranking.

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 provides query examples like 'best crypto casino 2026', 'safest bitcoin casino', which tell the agent when to invoke it. However, it does not mention when not to use it (e.g., for single casino details use 'check_casino') or alternative sibling tools for other use cases.

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