get_pending_transports

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

Discloses behavioral traits beyond annotations (none provided): shows CPU cost, deadline, resumability; expired refunded within ~1 minute; reuse rejected. Does not mention auth or rate limits, but for a 0-param read tool, this is minor.

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?

Four sentences, each carrying essential information: purpose, contents, action, and warnings. Front-loaded and efficient with no waste.

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?

Despite no parameters or output schema, the description fully covers what the tool does, what it returns, and how to interpret results. Compensates for lack of formal return specification.

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?

No parameters exist, so baseline 4 applies. The description adds context about what each entry contains (CPU cost, deadline, resumable), which is beyond the schema's empty definition.

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 it lists paid transports awaiting on-chain payment, distinguishing it from siblings like list_my_transports. It specifies the resource ('pending transports') and the action ('list').

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?

Explicitly tells when to use this tool (to see pending transports) and provides actionable guidance: finish paying with resume_transport for resumable ones, or wait for expired ones to auto-refund. Also warns against reusing a pending route.

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