earn_get_summary

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

No annotations are provided, so the description must fully convey behavioral traits. It indicates the data is private ([PRIVATE]) and states it returns a summary, but it does not disclose that it is a read-only operation, authentication requirements (optional jwt), or any rate limits or side effects.

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 very concise, with four short sentences. Each sentence adds value: purpose, details, usage guidance, and privacy note. No superfluous text.

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?

Given the tool's low complexity (single optional param, no output schema), the description is mostly complete. It explains what is returned (total rewards, breakdown, performance) and indicates it is private. A brief note on return format or that results are unfiltered would improve it, but not essential.

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?

With 100% schema coverage (one parameter fully described in schema), the description adds no additional meaning to parameters. It does not mention jwt, leaving schema to handle it. Baseline 3 is appropriate.

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 clearly states it returns a summary of accumulated rewards in Staking/Earn, including total rewards, breakdown by symbol, and performance. This distinguishes it from sibling tools like earn_get_positions (specific positions) and earn_get_rewards_config (configuration).

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 explicitly says 'Use this to see your total staking rewards,' which provides clear guidance on when to use this tool. However, it does not mention when not to use it or provide alternatives among siblings.

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