stellar_tx_manage_buy_offer

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

No annotations are provided, so the description carries the full behavioral burden, and it under-delivers. It does not disclose that this mutates on-chain state (delete is destructive/irreversible), that it signs and submits a transaction unless build_only is set, or what permissions/funds are required.

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?

A single front-loaded sentence with no filler and no repetition. It is efficient, though it is arguably too thin for a 9-parameter mutation tool, which keeps it just short of the top score.

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 6-required-parameter state-mutating tool with no annotations and no output schema, the description is inadequate. It omits the build-only vs. submit flow, network selection implications, signing requirements, and the destructive nature of the delete mode.

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% across all 9 parameters, so the schema already explains selling/buying/price/amount/network/offer_id/build_only. The description adds only the create/update/delete framing, which loosely maps to offer_id semantics but adds nothing 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 specific verbs (create, update, delete) plus a concrete resource (buy offer on the DEX). The 'buy' qualifier implicitly separates it from the sibling stellar_tx_manage_sell_offer, but the description never names that alternative explicitly, so differentiation relies on the reader noticing the name.

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?

The three operations are named, but there is no guidance on when to use this vs. stellar_tx_manage_sell_offer or stellar_tx_path_payment, and no prerequisites (signing, sequence, fee) are mentioned. The only usage hint, that offer_id=0 means a new offer, lives in the schema, not the description.

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