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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real value by disclosing the payload's contents (amounts, cooldown, bonds, tier, effective limits) in the absence of an output schema, though it does not explain units or what a 'bond' represents.

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?

A single dense sentence with the subject front-loaded and the conditional caveat placed early. Every listed item adds information; only the mid-sentence parenthetical slightly fragments the flow.

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, self-scoped lookup with no output schema, enumerating the returned fields is the key missing piece and the description supplies it. It falls short of 5 only because semantics of terms like cooldown and bonds are left unexplained.

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, which is the baseline-4 case; nothing in the description contradicts or under-specifies the empty schema.

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 resource ('Your stake') and enumerates exactly what it covers: staked, locked and unlocked amounts, cooldown, task bonds, tier and effective limits. That content distinguishes it well from get_balance and get_spend_limits, even though no sibling is named explicitly.

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 parenthetical '(where staking is enabled)' implies a precondition, but there is no explicit statement of when to call this versus get_balance, get_spend_limits, or get_me, and no guidance on what happens when staking is disabled.

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