stellar_xdr_encode

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 says nothing beyond the bare transformation. It does not disclose how output differs across the outputFormat enum, how invalid JSON or unknown types are handled, or whether the operation is purely local and side-effect free.

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 grammatical sentence with zero filler, and the verb-first phrasing front-loads the operation. It is efficient, though arguably terse for a five-parameter tool.

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 tool with 5 parameters, no annotations, and no output schema, one sentence is not sufficient. An agent gets no help understanding required input shape, type selection semantics, or the meaning of the different output formats.

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% and there are 5 well-documented parameters with 3 enums, so the schema already carries parameter meaning and a baseline of 3 applies. The description adds no syntax, format, or inter-parameter detail beyond what the schema states.

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 a specific verb (Encode) and both the source and target resources (JSON data to XDR format), which implicitly contrasts with the sibling stellar_xdr_decode. It does not, however, differentiate itself from other XDR siblings such as stellar_xdr_generate_default or stellar_xdr_guess.

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?

There is no guidance on when to use this tool versus stellar_xdr_decode or the other XDR utilities, nor any stated prerequisites, context, or exclusions. The agent must infer usage entirely from the name.

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