stellar_tx_manage_sell_offer

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

No annotations provided, so description carries full burden. It does not disclose that this submits a transaction on-chain (mutation), whether build_only means signing is skipped, what permissions/sequence requirements exist, or any rate limits. 'Manage' implies mutation but nothing specifies irreversibility, fees, or submission behavior.

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?

Very concise single sentence, front-loaded with the verb set and target resource. No wasted text, though also no elaboration.

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 9-parameter, mutation-oriented DEX operation with no annotations and no output schema, this is under-described. A calling agent lacks context on submission behavior, create/update/delete selection, and confirmation semantics.

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 baseline is 3. The description adds no parameter meaning beyond the schema, but the schema itself is comprehensive (asset format CODE:ISSUER, stroops, offer_id=0 for new offer, build_only semantics).

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) and resource (sell offer on the DEX). Clearly distinguishes from sibling stellar_tx_manage_buy_offer. However it does not differentiate by what constitutes 'manage' beyond the three operations named.

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 when-to-use or when-not-to-use guidance. Does not explain how create vs update vs delete are selected, or how this differs from manage_buy_offer. The offer_id parameter hints at update/delete but the description doesn't tie it together.

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