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

The description reveals live ccxt quotes and a FRED DEXKOUS conversion, which are open-world external dependencies, but the annotations declare openWorldHint=false. This contradicts the annotation and undermines the agent's assumptions about determinism and external data access. Per rubric, an annotation contradiction drops this to 1.

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?

Three sentences, each earning its place: scope in sentence one, valuation sources in sentence two, aggregation/currency behavior in sentence three. It is front-loaded and free of filler.

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 a no-argument tool with an output schema, the description covers asset coverage, per-asset valuation method, return/allocation outputs, and currency aggregation. Nothing an agent needs to select and invoke it correctly is missing, aside from the annotation inconsistency already penalized.

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?

There are zero parameters, so the schema already fully documents the input side. The description doesn't need to add parameter semantics, and it doesn't introduce any misleading input expectations.

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: 'Return the user's whole portfolio,' then enumerates asset classes and outputs such as valuation, return, and allocation. This clearly distinguishes it from sibling get_* tools as the aggregate portfolio view rather than a market/ticker/screener tool.

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 use case is implied (obtain an overall portfolio snapshot), but the description never tells the agent when to prefer this over siblings like get_stock_prices or import_portfolio, and it names no exclusions. With 35 siblings, explicit routing guidance would strengthen it.

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