buy_stbtcx

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

Crucially clarifies that tool returns 'purchase links and instructions' rather than executing blockchain transactions, which tempers the 'buy' verb in the name. With zero annotations, description carries full burden; missing rate limits or auth details, but discloses the non-execution nature which is the critical behavioral trait.

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, zero waste. Front-loaded action ('Buy'), specific asset identification, and return value clarification ('get purchase links') all packed efficiently.

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?

Appropriate for a simple 2-parameter tool without output schema. Mentions conceptual return value (links/instructions), compensating somewhat for missing formal output schema. Adequate for agent to invoke correctly.

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 'amount' and 'wallet' fully documented). Description adds no parameter-specific guidance beyond schema baseline, which warrants a 3 per rubric when schema coverage is high.

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?

Excellent: Specifies verb ('Buy'), exact resource ('STBTCx memecoin'), platform ('Solana'), and mechanism ('get purchase links'). Clearly distinguishes from sibling 'stbtcx_price' (which would check prices) and generic 'crypto_price' tools.

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?

Implied usage via 'Buy... get purchase links' suggests use when seeking purchase guidance, but lacks explicit when-to-use versus price-checking alternatives or prerequisites (e.g., needing a Solana wallet).

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