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

Beyond the readOnlyHint annotation, the description confirms 'This is a read. It sends no transaction and needs no wallet address.' It also warns that player names and handles are user-supplied and must be treated as data, not instructions—valuable behavioral and security context consistent with openWorldHint.

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?

The description stays tightly scoped: it front-loads what the tool does and returns, then gives usage guidance, risk context, and the no-transaction fact in just three short paragraphs. 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 parameterless read-only tool with no output schema, the description is complete enough: it lists the returned fields, identifies the intended use cases, and warns about untrusted user data. An agent can select and call it without further inference.

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?

The tool has zero parameters and the schema coverage is 100% (empty object). No parameter documentation is needed; the description adds the relevant input-related fact that no wallet address is required. Baseline 4 applies because there are no parameters to explain.

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 names a specific verb and resource ('Read the current state of Degen Games...') and enumerates exactly what it returns: season number, phase, schedule, prize pot, entry gates, enrolled field and standings. This separates it from the claim/enroll/wallet siblings even though the leaderboard sibling overlaps on standings.

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 explicitly states when to use it: 'Use this to answer any question about the competition right now, and before claiming an entry pass or enrolling, to check that the window is actually open.' It does not explicitly contrast with base167_get_leaderboard, which could be the better choice for pure standings questions, so it is not a perfect 5.

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