fluid_get_vault_data

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

With no annotations, the description must disclose behavioral traits itself. 'Get' implies a read operation and the listed return data gives insight into output, but it does not explicitly state that it is read-only, mention any prerequisite RPC usage, or describe error behavior. The missing rpc_url semantics are a transparency gap.

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 a single, well-structured sentence that front-loads the core action and resource, followed by a detailed list of returned data. Every element is informative, with no fluff or repetition.

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 provides a thorough list of return fields, which is essential given the lack of an output schema. However, the unexplained rpc_url parameter and lack of error handling or optionality details mean it is not fully complete for all usage scenarios.

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?

The schema already describes chain and vault_address, and the description reinforces the notion of a 'specific' vault, but adds no new parameter meaning. rpc_url has no description in either the schema or the description, leaving a gap for that optional parameter.

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 retrieves comprehensive data for a specific Fluid vault, enumerating supply/borrow tokens, rates, collateral factor, LTV limits, and availability. This specific resource and verb distinguish it from sibling tools that handle all vaults or user positions.

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 phrase 'for a specific Fluid vault' establishes a clear context for single-vault queries, implying this is for individual vault lookups rather than batch operations. However, it does not explicitly name alternative tools like fluid_get_all_vaults or state exclusions, so it falls short of full when/not guidance.

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