get_compound_positions

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

Annotations already mark it as readOnly, idempotent, non-destructive. Description adds specific return fields (supply/borrow balance, collateral, valuations) and edge case behavior (empty list if no exposure), confirming safe read operation.

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?

Two sentences efficiently pack purpose, return details, usage context, and edge case. Front-loaded with action verb. No redundant information.

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?

Covers all necessary aspects for a read-only tool: what it does, what it returns, when to use, and empty result handling. Lacks explicit return structure details, but given no output schema, the listed fields are adequate.

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 100% with descriptions for both parameters. Tool description mentions 'selected chains' but schema already covers default behavior. Minimal additional value beyond schema.

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?

Description specifies the exact verb 'Fetch', resource 'Compound V3 positions for a wallet', and scope 'across all known markets on selected chains'. It lists returned data fields (supply/borrow, collateral, USD valuations) and distinguishes itself from siblings by recommending use before prepare_compound_* actions.

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?

Explicitly states when to use: to answer 'my Compound positions' or before preparing a Compound action to get the market address. Provides interpretation of empty result. Does not explicitly exclude other uses, but context is clear.

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