morpho_get_positions

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

With no annotations, the description fully discloses behavior: returns specific position fields, explains health factor calculation, net value formula, and default multi-chain scan. Provides protocol context (looper detection, health warnings) that goes beyond a simple 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?

Well-structured with front-loaded purpose and clear sections. Some redundancy (e.g., 'Useful for understanding' and later 'The position shape reveals the strategy'). Could be slightly more concise, but every sentence adds value.

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?

Given no output schema, description sufficiently explains return structure (collateral, borrows, supply, vaults, health factors). Covers protocol context and cross-chain behavior. References sibling tools for deeper insights. Complete for a data query tool.

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%; both parameters have descriptions. The description adds context: chain enum values are listed, default behavior (scan all chains) is clarified, and the address regex is implied. Adds value beyond schema by explaining the purpose of each 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?

Description clearly states it queries a user's Morpho positions across markets and vaults, listing returned data (collateral, borrows, supply, vault deposits, health factors, signals). Distinguishes from siblings like morpho_list_markets, morpho_get_rate, and spectra_get_portfolio.

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 explains when to use this tool (understanding wallet holdings) and cross-references siblings. Provides protocol context including health factor formula and chain scanning behavior. Tells agent to specify chain to narrow scope, and points to morpho_list_markets for PT markets.

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