fluid_get_user_vault_nft_ids

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the basic action of getting NFT IDs, without mentioning return format, side effects (or lack thereof), limitations, or any prerequisites. The 'all' implies comprehensiveness but no further detail is given.

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, front-loaded sentence that is concise and free of unnecessary words. It earns its place by clearly stating the tool's purpose.

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?

For a simple getter with no output schema, the description provides adequate context: it returns all vault position NFT IDs for a user. However, it could be more complete by noting the return type or any potential edge cases, but given the simplicity, a score of 3 is appropriate.

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 documents two of three parameters (chain, user_address), but the tool description adds no additional meaning beyond the schema. The rpc_url parameter lacks a schema description and the tool description does not compensate, leaving this parameter under-explained.

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's function: to retrieve all vault position NFT IDs for a specified user address. It uses a specific verb ('Get') and resource ('vault position NFT IDs'), and distinguishes it from sibling tools that focus on other aspects like vault type or individual 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 description implicitly indicates when to use it (when you need a user's vault NFT IDs) but does not explicitly state when not to use it or mention alternatives. Given the sibling tools are contextually available, the usage context is clear but not explicitly differentiated.

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