get_dev_total_earnings

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

No annotations are provided, so the description must disclose behavioral traits. It implies a read-only query but does not mention authentication requirements (the default wallet hint is minimal), rate limits, data freshness, pagination, or whether the result is a sum or per-token breakdown. The absence of an output schema further compounds this gap.

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 a single, clear sentence that directly states the tool's function. No extraneous information; every word adds value.

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 absence of an output schema, the description should have clarified the return format (e.g., single number vs. list). The phrase 'lifetime distributed USDB earnings across every token' suggests aggregation but is ambiguous. For a simple tool with one parameter, this is minimally adequate but leaves gaps.

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 input schema covers the single parameter 'dev' with a description already including the default behavior. The tool description adds no additional semantic information about the parameter or its relation to the result, so with 100% schema coverage, a baseline score of 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 the tool retrieves a dev's lifetime distributed USDB earnings across all tokens they have a share on. The verb 'Get' and the specific resource 'lifetime distributed USDB earnings' make the purpose unambiguous and distinguishable from sibling tools like get_balances or get_creator_earnings, though an explicit differentiation would strengthen it.

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?

No guidance is provided on when to use this tool versus alternatives like get_creator_earnings or get_balances. The description only states what the tool does, leaving the agent to infer context from the name alone.

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