refresh_portfolio_data

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

The description says 'force refresh' implying a mutation action, but provides no details on side effects, rate limits, or what happens to existing data. With no annotations, more context about the refresh process would help.

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 a single, well-structured sentence that conveys the tool's purpose without unnecessary words.

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?

The description lacks information about return value (no output schema), error handling, or whether the refresh is asynchronous. For a mutation tool, these details would improve completeness.

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?

No parameters exist (input schema is empty and schema coverage is 100%). The description does not need to add parameter information, so a high baseline score is appropriate.

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 refreshes all portfolio price data from Yahoo Finance, including current and historical prices. It uses a specific verb ('refresh'), identifies the resource ('portfolio price data'), and distinguishes from sibling read-only tools like get_portfolio_pnl.

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?

No guidance on when to use this tool vs alternatives. Siblings are query tools for reading data, but the description does not mention scenarios like stale data needing refresh or any prerequisites.

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