Seller Statistics

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

Beyond the readOnlyHint/idempotentHint annotations, the description discloses the auth requirement (wallet signature identity) and, importantly, that the totals are lifetime while the chart is daily — implying the time filter scopes only the chart. 'Read-only' merely restates the annotation, and no error/permission-failure behavior is described, so it stops short of 5.

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?

Three tight sentences, front-loaded with what is returned, followed by the use case and the prerequisite. No filler and nothing repeated.

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?

An output schema exists, so return shape need not be spelled out; annotations cover the safety profile; the description covers identity requirements and the totals-vs-chart distinction. Nothing an agent needs in order to invoke this correctly is missing.

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?

Schema coverage is 100%, so the schema already documents both enums, making 3 the floor. The description adds real meaning on top: framing the parameters around a lifetime-totals-plus-daily-chart output clarifies that resourceType and the time window affect the chart rather than the lifetime aggregates.

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 uses a specific verb and resource: 'Read the logged-in seller's lifetime totals (delegations, resource delegated, TRX earned, average price per resource) and a daily earnings chart.' It even enumerates the chart's breakdown dimensions (auto, manual, exclusive, extend), so an agent knows exactly what comes back. It does not, however, name or contrast itself with any sibling (e.g. tronsave_get_user_info or tronsave_list_delegations), which keeps it at 4 rather than 5.

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?

'Use for "how much did I earn" questions' supplies a concrete triggering intent, and 'Requires a wallet signature identity' states the prerequisite before the call is attempted. There is no explicit when-not or named alternative, but the usage context is clear enough to route an agent reliably.

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