Update price

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

The description adds value beyond annotations by explaining that the tool upserts by date and, if the newest observation, updates the holding's current price to refresh portfolio values. This is important behavioral context that annotations (destructiveHint: true) do not fully capture. No contradiction with 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 two sentences with a clear structure: action, upsert behavior, side effect, and when to use. It is concise and front-loaded with the verb 'Record,' making it easy for an agent to parse quickly.

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 no output schema, the description adequately explains the tool's effect (upsert, portfolio refresh) and parameter units. It does not explicitly mention behavior for non-newest observations, but the core functionality is well-covered for a mutation tool.

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 input schema has 100% description coverage, so the baseline is 3. The description reinforces that price is in AUD per unit and implies the date is used for upsert matching, but these are already clear from the schema. No additional semantics beyond the schema are provided.

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 states the tool records a price observation for a holding. It specifies the action (record) and resource (price observation), and provides examples of sources. It is distinct from sibling tools like record_cost or record_income, which handle different transactions.

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 advises using the tool 'when you have an updated valuation or a reliable quoted price,' giving clear context for appropriate usage. It does not explicitly state when not to use it, but the context is sufficiently clear for an AI agent to make decisions.

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