paradex_vault_transfers

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

Annotations already declare readOnlyHint=true, so the description primarily adds context about auditing and reconciliation purposes. It does not disclose behaviors beyond that, such as pagination, rate limits, or data freshness. The additional context is useful but not extensive.

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 well-structured with bullet points and example use cases, front-loading the primary purpose. While it is somewhat lengthy, every sentence adds value. A slightly more concise version would be ideal, but it remains effective.

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?

Given the tool's simplicity (1 parameter, output schema present, annotations complete), the description provides comprehensive context for usage, including multiple use cases and a clear audit/reconciliation framing. It is fully adequate for the tool's complexity.

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% (vault_address described). The description does not add significant meaning beyond the schema for the single parameter, as it focuses on the tool's overall purpose. Baseline of 3 is appropriate since schema covers the parameter adequately.

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 the tool tracks deposit and withdrawal history for auditing and reconciliation. It uses specific verbs ('track', 'verify', 'audit') and resource ('deposit and withdrawal history'). It effectively distinguishes from sibling tools like paradex_vault_balance or paradex_vault_summary by focusing on historical movements.

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 lists specific when-to-use scenarios (verify deposits, track withdrawal status, audit fund flow, reconcile, understand patterns) and provides concrete example use cases. However, it does not explicitly state when not to use or mention alternative tools, which is a minor gap.

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