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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered; the description's additional value is the wallet-signature identity requirement and the fact that results are scoped to the logged-in seller (self-only, no user parameter). The trailing 'Read-only' merely restates the annotation rather than adding information, which holds it below a 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?

Two well-built sentences front-load the returned data and then route to the alternative, with no filler. The final 'Read-only' is redundant given readOnlyHint=true and is the one sentence that does not earn its place.

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?

With an output schema, full parameter documentation and read-only annotations, the description covers what matters: scope, return contents, alternative tool, and auth requirement. The one soft gap is that it says a wallet signature is required but does not point to the login/session tool that establishes it.

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 description coverage is 100% and both parameters are enums with documented meanings and defaults, so the schema carries the semantic load. The description only alludes to the resource dimension ('per resource') and never explains the chart window parameter, so it adds little beyond the schema — baseline 3.

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 verb ('Read') and a precisely enumerated resource: lifetime totals for delegations, resource delegated, TRX earned, average price, plus a daily earnings chart split by delegation type. It also names the sibling (`tronsave_list_delegations`) that returns the underlying rows, so an agent can distinguish the two without opening schemas.

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?

Gives an explicit selection rule ('Use for how much did I earn totals') and an explicit alternative with its condition ('for the individual delegations behind them use tronsave_list_delegations'). It also states a prerequisite ('Requires a wallet signature identity'), so the agent knows the call will fail unauthenticated.

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