get_pending_orders

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

No annotations are provided, so the description carries the full disclosure burden. It usefully defines 'pending' as 'open' and notes orders are across various DEXes, but says nothing about authentication needs, read-only nature, pagination, or what an empty result means for a read tool operating on wallet data.

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?

Two short sentences, zero filler, with the core action front-loaded in the first clause. The parenthetical gloss on 'pending' is a compact clarification rather than redundancy.

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 single-parameter read tool with no output schema, the description covers the basics but leaves the key ambiguity unresolved: how it differs from get_wallet_orders. An agent has enough to call it, but not clearly enough to choose it correctly.

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%, with the single address parameter fully documented (bech32, addr1 prefix). The description only restates 'Cardano wallet address', adding no syntax or format detail beyond the schema, so baseline 3 applies.

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 (Get) and resource (pending swap orders) with scope (for a Cardano wallet address), and clarifies that 'pending' means 'open'. However, it does not differentiate itself from the sibling get_wallet_orders, which an agent could easily confuse it with.

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 the retrieval context but gives no explicit when-to-use guidance, no conditions that select it over get_wallet_orders or get_all_dca_orders, and no exclusions. The agent must infer the distinction purely from naming.

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