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

With no annotations supplied, the description carries the full burden and does state 'Read only' plus the auth requirement (operator key linked with link_account), which is the key behavioral fact an agent needs before calling. It also discloses the returned fields in detail despite no output schema, though it omits what happens when no operator key is linked (error vs. empty result).

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 core purpose, followed by a compact enumeration of returned data and two short constraint sentences. The long enumerated clause is dense but each item adds distinct information, so little is wasted.

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 tool with no output schema, the description covers purpose, return contents, safety (read only) and authentication, which is essentially everything needed to invoke it. Only failure behavior when the account is unlinked is left unstated.

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 there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. The description correctly implies the target account is determined by the linked operator key rather than by arguments.

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?

States a specific verb and resource: the limits the linked account's owner set for place_bet and play_dice, then enumerates exactly what is returned (on/off flags, per-bet and per-day caps in sats, 24h staked and remaining, deposited cash balance). That enumeration distinguishes it from neighboring tools like get_rate_limits, get_spend_policy and get_budget_status, which cover different limit domains.

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?

The description gives a hard prerequisite (an operator key linked via link_account) and implies usage by reporting 'what has been staked in the last 24 hours and what is left', but it never explicitly says when to call this instead of get_spend_policy, get_budget_status or get_rate_limits, nor does it state any when-not conditions.

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