show_portfolio

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

No annotations provided, so description carries full burden. It describes what data is computed (from transaction log, snapshot history) and what optional features exist. However, it does not explicitly state it is read-only or mention data freshness.

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?

Two sentences: first enumerates output contents, second provides usage guidance. Every word adds value, no redundancy.

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 lists all major output fields (ticker, shares, avg cost, etc.) and optional elements. Could be improved by specifying return shape (object/array) and any time constraints, but sufficient for agent to understand what is returned.

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 single parameter 'currency' is fully described in schema; the description adds that it triggers FX decomposition per holding when non-USD. Schema coverage is 100%, and description adds behavioral context beyond schema.

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?

Description clearly states it shows current holdings with detailed fields (ticker, shares, avg cost, etc.) and optional risk summary and FX decomposition. Distinguishes itself from sibling tool get_brief by recommending it for daily check-in.

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?

Explicitly advises when to use get_brief instead ('for the daily check-in, prefer get_brief'), providing clear alternative context. Also describes when currency parameter triggers FX decomposition.

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