paradex_vaults

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

Annotations already declare readOnlyHint=true, so the description's job is lighter. It adds value by stating the tool retrieves 'comprehensive details... including configuration, permissions, and other vault-specific parameters,' which is behavioral context beyond the annotation.

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 front-loaded with the core purpose and then provides examples. It is efficient but includes several JMESPath examples that are valuable, though slightly lengthy. Every sentence earns its place.

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 has no output schema, the description sufficiently explains the tool's behavior, input parameters, and filtering capability. It covers the main use case and provides necessary constraints (large number of vaults). It is complete for a list/detail retrieval 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 description coverage is 100%, so baseline is 3. The description adds meaning by explaining that vault_address can be empty to get all vaults, and provides examples for jmespath_filter usage, going beyond the schema descriptions.

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 states 'Get detailed information about a specific vault or all vaults if no address is provided,' clearly identifying the verb and resource. It distinguishes between fetching a specific vault or all vaults, and among sibling vault-related tools, this one is uniquely about vault details.

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 includes explicit guidance to 'Use jmespath_filter to reduce the number of results as much as possible as number of vaults can be large,' providing clear context for when to use filtering. However, it does not specify when to prefer this tool over alternatives like paradex_vault_summary.

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