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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, and the description reinforces 'Read-only'. It adds genuinely new context by disclosing that a wallet-signature identity is required, which is an auth prerequisite an agent must arrange before calling. Nothing is contradicted, though pagination behavior beyond the schema is left implicit.

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: what is listed and what fields, then the routing/sequencing tip, then the auth and safety notes. Front-loaded and free of redundancy.

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 an output schema exists and annotations carry the safety profile, the description supplies the remaining essentials: returned fields, prerequisite identity, and use-before-mutation guidance. Only the pagination contract is left entirely to the schema, a minor gap.

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%, with limit, offset and filterBy each fully documented in the schema, including the max-10 cap and pagination semantics. The description adds no parameter-level meaning beyond that, so baseline 3 applies.

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 ('List') and resource ('auto-buy rules') and enumerates the fields returned (receiver, resource, unit price cap, threshold, budget limits, totals, active state). That level of specificity lets an agent distinguish it from the sibling mutation tools and from tronsave_get_user_auto_setting.

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 explicit sequencing guidance: call this before tronsave_update_auto_buy_setting or tronsave_delete_auto_buy_setting to obtain rule ids. It does not clarify when to prefer this over related reads like tronsave_get_user_auto_setting, so it falls short of full when/when-not coverage.

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