stellar_xdr_encode

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

The description indicates a pure encoding operation with no side effects, but fails to disclose error handling, output format details, or any constraints. Since no annotations exist, the description carries full burden; it is adequate but could be more explicit.

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 a single, well-structured sentence that front-loads the key action and includes a helpful parenthetical about roundtrip. No wasted words.

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 straightforward encoding tool with two parameters and no output schema, the description covers the basic purpose and links to complementary tools. It is complete enough for typical use, though specifying the output type would enhance completeness.

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 provides clear descriptions for both parameters (type and json). The description adds workflow context but no additional parameter-level semantics. With schema coverage at 50%, the description does not compensate significantly.

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 encodes JSON to base64 XDR for a named type, and references related tools (stellar_xdr_json_schema and decode tools) to establish its role in a roundtrip workflow. This distinguishes it from siblings like stellar_decode_xdr, stellar_xdr_guess, and others.

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 description implies usage after obtaining a schema and before decoding, but does not explicitly state when not to use this tool or list alternatives. The mention of 'roundtrip' provides context, but more precise guidance would improve clarity.

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