get_safe_positions

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

Annotations already declare read-only and idempotent. Description adds behavioral details: requires API key authentication, returns pending and recently-executed transactions, risk notes, and union/dedup behavior. No contradictions.

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?

Description is front-loaded with purpose and well-structured, but somewhat dense. Every sentence earns its place with no redundancy, though could be slightly more concise.

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 adequately covers return structure (threshold, owners, version, balance, transactions, risk notes). Also mentions prerequisites (API key), limitations (no ERC-20), and cross-references related 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?

Schema has 0% description coverage; description fully explains each parameter: signerAddress for wallet discovery, safeAddress for direct lookup, chains with default ethereum and supported values. Adds meaning beyond schema patterns.

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?

Clearly states it fetches Safe multisig accounts for an EVM owner address and/or by Safe address, listing returned fields. Distinguishes from siblings by explicitly noting ERC-20 balances are not included and directing to get_token_balance or get_portfolio_summary.

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 signerAddress (discover all Safes for a wallet) vs safeAddress (look up one Safe), and that both can be used together. Describes chains default behavior and requirement for SAFE_API_KEY, also notes what the tool does not cover (ERC-20 balances) with alternatives.

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