list_outgoing_transfers

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

With no annotations, the description carries the full burden. It specifies the HTTP GET method and mentions the preview_path for deep-linking, implying a read-only operation. However, it does not explicitly state that no mutations occur, nor does it disclose any side effects or authentication requirements beyond the implicit wallet 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?

Two sentences with clear front-loading: first sentence conveys core purpose, second adds a key detail (preview_path) and the API call. No redundancy or unnecessary text.

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?

The description specifies the returned data includes preview_path, but lacks details about the full response structure or pagination behaviour. Given the tool's simplicity and the presence of pagination parameters, a brief note on how to iterate pages would improve completeness. Still, it covers essential context for an agent to begin using the tool.

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 coverage is 100% (two parameters: after and limit). The description does not add meaning beyond the schema; the schema already describes 'after' as an opaque cursor and 'limit' as page size with default 50. The description's mention of preview_path is unrelated to parameters, so no additional semantic value.

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 pending project transfers initiated by the authenticated wallet, distinguishing it from incoming transfers and other transfer-related siblings like list_incoming_transfers, initiate_project_transfer, etc. It also mentions the API endpoint and the preview_path field.

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 usage for outgoing initiated transfers, but lacks explicit guidance on when to use this tool versus alternatives such as list_incoming_transfers, preview_project_transfer, or accept_project_transfer. Context from sibling names fills the gap, but the description itself does not provide exclusion criteria.

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