stellar_sep24_interactive

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

The description mentions returning an interactive URL but fails to disclose any side effects, authentication requirements (though token is required), or error handling. Since no annotations are provided, the description should carry more burden.

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?

The description is only two sentences, with no wasted words. It is front-loaded with the core action and return value.

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?

The tool has 4 required parameters and no output schema, yet the description does not elaborate on the return value format (e.g., URL expiration, additional fields). It also lacks context about prerequisites like SEP-10 authentication.

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?

The input schema already describes all four parameters with 100% coverage (anchorDomain, type, assetCode, token). The description does not add any additional meaning beyond what the schema provides, so baseline score of 3 is appropriate.

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 description clearly states that the tool initiates a SEP-24 interactive deposit or withdrawal and returns a URL. However, it does not differentiate from related sibling tools like stellar_sep6_transfer, which also handles transfers.

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 guidance is provided on when to use this tool versus alternatives like stellar_sep6_transfer. The description lacks exclusions or context for appropriate use.

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