Register Selling Pool

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

Discloses that the tool creates a pool and auto-selling configuration, requires subsequent permission granting, and requires an API key. Without annotations, this is sufficient for a registration tool. Could be improved by mentioning if it is idempotent or destructive.

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 sentences, front-loaded with the main purpose. Each sentence adds value: purpose, requirement, and verification step. No wasted words.

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 no output schema and moderate complexity, the description covers the registration process, necessary permissions, and verification step. References sibling tool for checking permissions. Complete and actionable.

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 documents all parameters. Description only mentions paymentAddress, adding no extra meaning to the other three parameters. 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?

Clearly states the verb 'register' and the resource 'TRON address as an energy/bandwidth selling pool'. Distinguishes from sibling tools like check_pool_permissions and configure_auto_selling by specifying it creates the pool and auto-selling configuration.

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?

Provides explicit post-registration steps (grant permissions, use check_pool_permissions) and mentions API key requirement. Lacks explicit when-not or alternatives, but the context of sibling tools makes the use case clear.

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