getOffers

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

There are no annotations, so the description carries the transparency burden. It adds behavioral context by restricting results to 'open' offers rather than all offer history, but it does not describe pagination, ordering, error conditions, or explicitly confirm that the operation has no side effects beyond the verb 'Get'.

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, front-loaded sentence with no filler or redundancy. It names the operation and the scope in eight words, so every part earns its place.

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 simple read tool with one required parameter and full schema coverage, the description gives enough information for an agent to select and invoke it. An output schema or a note about response shape would improve completeness, but the core resource and scope are clear.

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?

Both parameters are already fully described in the input schema, with 100% schema description coverage. The description does not need to add parameter details; it simply aligns with the accountId parameter by mentioning 'a Stellar account'.

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 uses the specific verb 'Get' and names the resource 'open DEX offers' scoped to a Stellar account. It clearly communicates what is returned and is enough to distinguish it from sibling tools like getOrderbook or getTransactions.

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 explicit when-to-use or when-not-to-use guidance is given, and no alternative tool is named. The phrase 'for a Stellar account' implies this is the account-level offers tool, but an agent is left to infer the exact fit from the name and sibling list.

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