fluid_get_user_all_positions

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

With no annotations, the description must carry the full burden of behavioral disclosure. It only states what the tool returns ('combined fToken details and user position data') but does not disclose any side effects, permissions, error conditions, or the fact that it is a read-only operation. The description adds no behavioral context beyond the tool's name and basic return type.

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 two short sentences that directly state the tool's function and return content with no redundant words or filler. Each sentence earns its place, and the information is front-loaded with the primary action.

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 read tool with no output schema and no annotations, the description is somewhat minimal. It mentions the return type ('combined fToken details and user position data') but does not elaborate on the status of the optional 'rpc_url' parameter or any constraints on the chain parameter. The tool is simple, so the description is adequate but leaves room for more detail on expected outputs or usage prerequisites.

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 coverage is 67% (two of three parameters have descriptions), but the description adds no extra parameter semantics. It does not explain the undocumented 'rpc_url' parameter, and its mention of 'across all fTokens on a chain' merely restates the existing chain description. The description provides no value beyond the schema's parameter explanations.

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 verb ('Get') and resource ('all of a user's lending positions'), scoping it to 'across all fTokens on a chain'. It explicitly distinguishes from siblings like 'fluid_get_user_lending_position' (singular) and 'fluid_get_all_ftokens' (just fToken list) by adding the combination of fToken details and user position data.

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 provides clear context for when to use the tool: to retrieve all lending positions for a user across fTokens. It does not explicitly name alternative tools or state when not to use it, but the 'all positions' vs 'single position' differentiation is implied by the wording and sibling tool names.

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