transfer_stx

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

With no annotations, the description carries the full burden, and it does disclose the key trait that this signs and broadcasts on-chain ('Signs and broadcasts the transaction'), implying an irreversible write. However it omits prerequisites (unlocked wallet, sufficient balance), confirmation/return behavior (e.g., a txid), and irreversibility warnings.

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?

Front-loaded with purpose and mechanism, then a compact unit example; nearly every sentence earns its place. The trailing 'earning_opportunities' tip is tangential to the transfer action and slightly dilutes focus.

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?

For a value-moving tool with no annotations and no output schema, the description is thin on prerequisites and results. An agent still cannot tell from the description whether it needs an unlocked wallet, how failure looks, or what is returned after broadcast.

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%, so all five parameters including fee presets, sponsored relay, and memo are already documented in the schema. The description's micro-STX example reinforces the amount field but adds nothing beyond what the schema says.

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?

The first sentence gives a specific verb and resource ('Transfer STX tokens to a recipient address') and adds the mechanism ('Signs and broadcasts the transaction'), which distinguishes it from read-only siblings like get_stx_balance. It does not explicitly contrast with near-neighbors such as transfer_token, sbtc_transfer, or pillar_send, so an agent must infer which asset rail to use.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative is named for non-STX assets or for sending via a Pillar wallet. The only guidance is a unit-conversion example and an unrelated tip pointing to earning_opportunities, which is not a routing alternative for this action.

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