aureon_sync_portfolio

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

With no annotations, the description carries the full burden, but the word 'Replace' usefully discloses a destructive overwrite of the whole capital book. It stops short of stating auth requirements, reversibility, or failure behavior for a financial mutation.

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 no filler; the destructive action and its source are stated immediately.

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 destructive financial mutation with no annotations and no output schema, the description is too thin: it omits prerequisites, what data is discarded, and what a successful/unsuccessful sync looks like.

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 and schema coverage is effectively 100%, so the baseline of 4 applies. Nothing in the description is needed to disambiguate parameters.

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 verb ('Replace'), a target resource ('the capital book'), and a source ('on-chain balances for the session wallet'). This clearly distinguishes it from read-oriented siblings like aureon_get_portfolio, though it does not explicitly name set_portfolio/clear_portfolio as alternatives.

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 explicit guidance on when to use this versus aureon_set_portfolio or aureon_clear_portfolio, nor any stated prerequisites (e.g., wallet must be verified). The 'session wallet' phrasing weakly implies a logged-in context but nothing is spelled out.

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