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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered; the description goes further by disclosing the 30-day maturity rule and the external dependency on venue-portal identity/payout setup. It does not state anything about freshness, caching, or error conditions, so it falls short of a 5.

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, both dense with distinct information — the first covers wallet contents and the maturity rule, the second covers preconditions. No filler, and the most decision-relevant content (what's in the wallet, whether withdrawal is possible) leads.

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 zero-parameter, read-only tool with an output schema already documenting the return shape, the description supplies exactly the missing pieces: the domain maturity rule and the external preconditions. Nothing an agent needs to call or interpret it correctly is absent.

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 takes zero parameters, so the baseline is 4; there is nothing parameter-related the description could or should explain. The schema is trivially complete at 100% coverage.

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 enumerates the wallet's contents precisely: earned-from-adverts, matured (with the 30-day rule), paid, and withdrawal eligibility. An agent can tell this is the read-only state view rather than the sibling host.earnings.withdraw, though the sibling is only implied by 'whether a withdrawal can be requested' and never named.

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 supplies the operative context for the withdraw flow: a day's share matures after 30 days, and identity verification/payout details are configured on the venue portal, with this tool reporting if they are missing. That tells the agent when to call it as a precondition check, but there is no explicit when-not-to-use or direct pointer to host.earnings.withdraw.

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