stellar_submit_payment

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

No annotations provided, and the description omits critical behavioral details such as side effects (e.g., balance changes), authorization requirements, or error conditions for a payment submission.

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, front-loaded with the action and return value, no redundancy.

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?

Missing details on return value structure, prerequisites (e.g., trustlines for credit assets, account funding), and error handling, which are crucial for a payment tool with no output schema.

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%, so parameters are well-documented in the schema; the description adds minimal value beyond restating purpose.

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 the tool submits a Stellar payment and returns the transaction hash, distinguishing it from sibling tools that handle queries or other operations.

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?

Implies usage for sending payments but provides no explicit guidance on when to use this versus siblings like stellar_submit_fee_bump_transaction or stellar_set_options.

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