aureon_get_portfolio_history

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

No annotations are provided, so the description carries the full behavioral burden, and it states almost nothing beyond the resource: not whether the call is read-only, how far back the history reaches, how many entries are returned, or in what order. For a zero-parameter historical query these are the details that matter, and they are absent.

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 short clause with no filler and the key qualifier ('daily', 'stored') front-loaded. It is efficient, though arguably terse to the point of under-specification rather than tightly structured.

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 no output schema and no annotations, the description is the only source of contract information, and it covers the resource and granularity but not the time range, result size, or ordering. For a simple zero-parameter read this is marginally adequate, but an agent cannot predict what it will receive.

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 schema has nothing to explain and the baseline is 4. The description correctly introduces no parameter semantics because none exist.

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 names a specific resource and granularity ('daily portfolio totals') scoped to 'this wallet', and the word 'history' plus 'stored' implicitly separates it from the sibling aureon_get_portfolio, which returns the current portfolio. It stops short of explicitly naming that sibling or stating the contrast, so it is clear but not fully differentiated.

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 mention of alternatives such as aureon_get_portfolio or aureon_get_health_history, and no stated conditions or prerequisites. The agent must infer usage entirely from the name and noun phrase.

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