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

With no annotations, the description carries the full behavioral burden and does not meet it. It implies a read-only derivation from saved history but says nothing about what happens when no history exists, whether an account/wallet context is required, or how results are shaped.

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?

A single front-loaded sentence with zero filler; the metric list is dense but informative. The colon-separated enumeration is slightly unwieldy but every item earns its place as the actual return contents.

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 no-parameter tool with no output schema and no annotations, the enumeration of metrics partially substitutes for a return contract. However, it says nothing about the result shape (per-metric object? single values?) or the implied dependency on portfolio history being populated.

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?

The tool takes zero parameters, so the baseline is 4. There is nothing for the description to disambiguate, and it correctly does not invent parameter guidance.

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?

States a specific resource (advanced portfolio metrics) and enumerates exactly which metrics are returned, so an agent can see it differs from get_portfolio, get_pnl and get_portfolio_score. It does not, however, explicitly contrast itself with those siblings in words.

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 when-to-use guidance, no prerequisites and no named alternative. The phrase 'from the saved history' hints that history must exist, but the description never routes the agent between this and the many other portfolio/metric tools.

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