fluid_get_total_positions

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

No annotations are provided, so the description carries the full burden. It indicates a read operation ('Get'), which implies no state changes, but it does not disclose any additional behaviors such as return format details, error handling, or whether the count might be expensive. It is neither contradictory nor richly informative.

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 entire description is one concise, front-loaded sentence that conveys the essential purpose without any filler. It is immediately understandable and uses no unnecessary words.

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 tool is simple, but with no output schema, the description should clarify the return type (e.g., integer) and any prerequisites or caveats. It states 'total number' which implies a numeric result, but it does not explain whether the count is aggregated across all vaults with zero positions, nor does it address the optional rpc_url. Given the simplicity, the description is adequate but not fully complete.

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 description mentions 'on a chain', which ties to the required 'chain' parameter, but it completely ignores the 'rpc_url' parameter. Schema description coverage is only 50% (chain has a description, rpc_url does not), and the description does not compensate for the missing rpc_url semantics. No parameter guidance is added beyond what the schema provides for chain.

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 action ('Get'), the resource ('total number of vault positions (NFTs)'), and the scope ('across all vaults on a chain'). This distinguishes it from sibling tools like fluid_get_vault_position (which fetches a single position) and fluid_get_all_vaults (which lists vaults). The inclusion of 'total number' and 'NFTs' adds specificity.

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 'across all vaults' provides clear context for when to use this tool: when a global count is needed rather than details for a specific vault or user. However, it does not explicitly name alternatives or exclusions (e.g., 'for per-user positions, use fluid_get_user_all_positions'), so it falls short of the top score.

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