list_outgoing_transfers

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

Discloses HTTP method and endpoint, version requirement, and presence of 'preview_path' field. However, with no annotations, it omits side-effect disclosure (though GET implies idempotent) and error handling.

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 concise sentences conveying purpose, scope, key feature, and API endpoint. No redundant information.

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?

Provides essential info but lacks details on response structure (beyond preview_path), sorting, filtering, or default order. For a list tool with no output schema, more context would improve completeness.

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% with adequate descriptions for 'limit' and 'offset'. Description adds no extra nuance beyond schema, so baseline 3 is appropriate.

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?

Description clearly specifies the action ('List'), resource ('pending project transfers'), and scope ('INITIATED BY the authenticated wallet'). Version info and sibling differentiation are explicit.

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 guidance on when to use this tool versus its sibling 'list_incoming_transfers'. Absence of usage context or prerequisites limits agent decision-making.

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