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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the return contents in detail (vault deposit, USDC lent, WETH collateral, borrowed, health factor, liquidation price, rates), which is valuable given there is no output schema.

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?

It is a single dense sentence, but front-loaded on the primary resource and every clause carries substantive return information rather than filler. It could be broken into two sentences for readability, but nothing is wasted.

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?

With no output schema, the description does the heavy lifting of enumerating what comes back, and the sole required parameter is fully documented in the schema. Annotations cover the safety profile. The main gap is routing guidance relative to overlapping sibling read tools.

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?

With a single parameter and 100% schema description coverage, the schema already fully documents the wallet argument (format pattern, Base chain, ownership semantics). The description adds nothing beyond that, so the baseline 3 applies.

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 names the specific resources returned: the wallet's Curated Vault deposit (Steakhouse Prime USDC on Morpho) and its Morpho WETH/USDC lending position, plus rates and balances. That is far more specific than a generic 'get positions'. It does not, however, distinguish itself from siblings like get_wallet_positions or get_wallet_balances, which an agent must choose between.

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?

There is no explicit when-to-use guidance and no mention of alternatives, despite several sibling read tools (get_wallet_positions, get_old_vault_positions, get_wallet_balances) that overlap in scope. Usage must be inferred from the content list alone.

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