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

Annotations already provide the read-only, idempotent, non-destructive profile, and the description adds real behavioral context: the difference between concise and full response shapes, the presence of snapshot_id and chaining IDs, and the note that it persists as a PortfolioSnapshot for historical tracking. No wording contradicts 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 compact and dense: purpose, response behavior, and workflow are all packed into three short, structured paragraphs. More information is front-loaded, labels like detail="concise" are clear, there is no fluff, and referencing get_trading_workflow avoids repeating workflow details.

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 an output schema present, the description does not need to repeat exact return fields. It covers what the snapshot is, how detail changes the output, how the returned IDs compose with other tools, and the correct ORIENT workflow position. Together this is enough for an agent to call and use it successfully.

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 0%, so the description must compensate for the param meanings. It explains the critical detail parameter well, including default and response variants. However, caller_id and wallet_address are left undefined; wallet_address is inferable from the name but caller_id is not. The compensation is valuable but incomplete.

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 clearly identifies the resource and output: a full portfolio summary with positions, total value, allocation %, and 24h change. It does not start with an explicit verb, but the intent is immediately unambiguous. It could distinguish itself more from siblings such as get_balances or equity_positions by name, so it misses a 5.

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 context for when to use this: it names the ORIENT step, says it is the denominator for position sizing, and explicitly advises calling it before intelligence/risk. It does not spell out exclusions or name alternatives (e.g., 'use get_balances when...'), so it earns a 4 instead of a 5.

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