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

Explicitly says read-only and non-custodial, and clarifies that earnings settle to the withdrawal address on release. This goes beyond the readOnlyHint annotation by explaining the funds-flow behavior.

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 is reasonably compact, although the opening sentence and the detailed list overlap slightly. Overall it's focused and not padded.

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?

The description lists all major return categories and mentions read-only behavior. Since output schema exists, it doesn't need to reproduce exact return types, but it gives enough context for an agent to know what it will get.

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?

No parameters are defined, and the schema description explains the owner is derived from the authenticated principal. There is nothing ambiguous for an agent to fill in.

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 action (check) and resource (earnings), and enumerates what's included. It also distinguishes from sibling tools by focusing on read-only earnings status rather than funding, hiring, or contract actions.

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 makes clear this is for checking earnings and pending amounts, which implies when to use it. It doesn't explicitly contrast with sibling tools, but the purpose is unambiguous enough for selection.

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