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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the description's real contribution is the return semantics: what blocking vs. warnings mean, that blocking names a resolving tool, and the precise threshold behind can_post (>= $0.01 plus budget coverage). That is meaningful behavioral context beyond the annotations.

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?

Front-loaded with the payoff ('What you can do now'), then the field-by-field semantics, then the one actionable instruction. It is dense but each clause carries information; a slightly tighter grouping of the output fields could shave length without loss.

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?

With no output schema, the description carries the full burden of explaining return values, and it does so for every listed field including the non-obvious ones (blocking, warnings, next_step, can_post threshold). It is complete enough to call and interpret, though it omits any note on freshness/caching of the readiness snapshot.

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 per the rubric the baseline is 4; there is nothing for the description to disambiguate, and the empty schema leaves no ambiguity.

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 states precisely what the tool returns (readiness flags can_post/can_bid/can_withdraw, wallet balances, payout status, tier limits) and the shape of its output (blocking, warnings, next_step). It is clear, but it never contrasts itself with the sibling tools that expose overlapping data (get_balance, get_spend_limits, payout_status, get_terms_status), so the aggregation role must be inferred.

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 gives explicit timing guidance ('Call it before posting') and explains the resolution path through the blocking entries, which is genuinely actionable. It stops short of stating when-not to use it or naming the siblings it replaces, so no exclusions are offered.

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