get_strx_account

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

Annotations already declare readOnlyHint=true, destructiveHint=false, so the agent knows this is a safe read operation. Description adds no behavioral context beyond listing output fields; it doesn't disclose rate limits, auth needs, or other traits. No contradiction with annotations.

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?

Single sentence with clear verb and list of included fields. No fluff or redundant information.

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?

Despite no output schema, the description fully enumerates the key fields returned (staked amount, income, claimable rewards, withdrawn amount, rental energy amount). For a read-only tool with good annotations, this is sufficient for an AI agent to understand what it will receive.

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%: both parameters (address, network) have descriptions covering pattern, default, and optionality. The description adds no extra parameter meaning beyond listing output fields, so it meets baseline but does not exceed.

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?

Description clearly states it retrieves sTRX staking account info and enumerates specific fields (staked amount, income, claimable rewards, withdrawn amount, rental energy amount). This distinguishes it from siblings like get_strx_balance (balance only) and get_strx_dashboard (likely dashboard summary).

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?

No explicit when-to-use or when-not-to-use guidance is provided. The description implies use for detailed staking account info, but with many related sibling tools, some differentiation would help agents choose correctly.

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