Post Instances Create Asset Trustline

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true. The description adds nothing beyond that: it does not say whether creating a trustline is irreversible on-chain, whether it requires the asset issuer's authorization, or what side effects occur. No contradiction with annotations, but zero added behavioral context.

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?

Three words is not conciseness but under-specification; there is no structure to speak of and nothing is front-loaded because nothing is said. The brevity saves no reader effort since the agent must infer everything.

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 an open-world, non-idempotent mutation tool with a nested required body, no output schema, and undocumented parameters, the definition is far too thin. The annotations supply a basic safety profile, but key facts — required preconditions, reversibility, response shape — are absent.

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 33%: only Idempotency-Key is documented in-schema. 'instance_id' has format constraints but no prose, and the nested required 'address' is entirely ambiguous — the description never clarifies whether it is the asset issuer address, the asset identifier, or the network address. The terse description fails to compensate for the coverage gap.

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 'Create Asset Trustline' is essentially a restatement of the tool name and title, with no indication of which network (Stellar is implied only by the name), what an asset trustline is, or how it differs from blockchain-related siblings like PostV1InstancesPayoutsStellarAuthorize or PostV1InstancesPayoutsEvm. It states a mutation verb and a resource but adds no distinguishing detail.

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 when-to-use guidance, no prerequisites (e.g., that the instance must exist or the customer wallet be set up), and no mention of alternatives among the ~70 sibling tools. An agent has no basis to choose this tool over adjacent Stellar/payout operations.

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