Auto-Buy Rules

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

The annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety and cacheability are covered. The description adds a genuinely new behavioral fact the annotations lack: an authenticated wallet signature identity is required. 'Read-only' merely restates an annotation and the field inventory duplicates the output schema, so it stops short of 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 sentences, both front-loaded: the core action and returned data come first, then the workflow routing and auth prerequisite. Every clause carries information with no filler.

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 values need not be re-explained, and annotations cover the safety profile; the description still supplies the auth requirement and sibling workflow that an agent needs. It is only slightly short on paging/filtering guidance, which matters given the max-10 limit.

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 67%, with `limit`, `offset` and the `filterBy` enum documented in the schema. The description says nothing about pagination, page size limits, or when to use `filterBy`, so it adds no meaning beyond the schema; 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 and resource ('List the logged-in user's auto-buy rules') and enumerates the returned fields (receiver, resource, price cap, threshold, budget limits, totals, active state). It is clearly distinguishable from the create/update/delete auto-buy siblings named in the text.

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?

Explicitly directs the agent to call this before `tronsave_update_auto_buy_setting` or `tronsave_delete_auto_buy_setting` in order to obtain rule ids. It also states the prerequisite ('Requires a wallet signature identity'), so the agent knows both when and under what conditions to call it.

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