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

Annotations already mark destructiveHint=true and readOnlyHint=false, and the description adds substantial behavioral context beyond that: merge/replace semantics, live ccxt quotes for crypto and gold, direct-value storage for cash/physical/unsupported ETFs, and automatic watchlist registration. There is no contradiction with the annotations.

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 long but dense: each sentence covers a distinct asset category, pricing path, or caveat. It is front-loaded with the core purpose and then layers asset-type handling and parameter guidance. Minor restructuring could improve scannability, but there is little redundancy.

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 complex import tool, the description covers the essential behavioral surface: accepted asset types, database matching, live quote behavior, direct-value fallback, replace/merge semantics, category label handling, and the watchlist side effect. An output schema exists and annotations cover the destructive nature, so no major missing context remains.

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 description coverage is 100%, so the baseline is met, but the description adds cross-parameter guidance that the schema alone does not provide: when to pass asset_class, when to pass value directly instead of relying on pricing, and how price_symbol/unit interact for PAXG and TLT-style symbols. This adds meaningful decision guidance for the holdings array.

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 opens with a specific verb and resource: 'Register holdings read from a brokerage (MTS/HTS) screenshot or an asset table into the user's portfolio.' It clearly distinguishes itself from siblings like add_to_watchlist and get_portfolio by emphasizing bulk portfolio registration and the automatic watchlist side effect for listed stocks.

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 gives strong usage context: it should be used when importing holdings from screenshots or tables, covering stocks, cash, crypto, and physical assets. It does not explicitly name alternatives or state when not to use it, but the input-source framing and write behavior separate it from the read-only and screening sibling tools.

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