refresh_portfolio

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

With no annotations provided, the description bears full responsibility for revealing behavior. It states that the tool recalculates portfolio P&L and requires an API key. While it doesn't detail potential side effects or rate limits, the action 'recalculate' implies a write operation, and the requirement is disclosed. This is adequate for a simple tool.

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 extremely concise—two sentences that cover purpose, usage context, and a requirement. No unnecessary words, and the key information is front-loaded. Every sentence earns its place.

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 parameters and no output schema, the description covers the main points: what the tool does and when to use it. It mentions the API key requirement but does not describe the return value or error handling. For a simple recalculation tool, this is mostly complete.

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 has zero parameters, so the input schema fully documents them. The description does not need to add parameter details, and it appropriately avoids over-explaining. Baseline for 0 params is 4.

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 verb 'Recalculate' and the specific resource 'the user's portfolio P&L', making the tool's purpose unambiguous. It also distinguishes itself from sibling tools like get_portfolio_summary which likely reads rather than recalculates data.

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 provides explicit context for when to use the tool ('after recording a batch of transactions if you want immediate fresh numbers') and mentions a requirement ('Requires IWMM_API_KEY'). However, it does not explicitly name alternatives or state when not to use it.

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