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

With no annotations provided, the description carries the full burden of behavioral disclosure. It names output fields but does not state whether the operation is read-only, what authentication is needed beyond the api_key parameter, or any other behavioral traits. This is a significant transparency gap.

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 short noun phrase, not a complete sentence, which is concise and without fluff. However, it is under-specified, lacking a verb and any structural framing that would make it a proper tool description.

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 simple tool with one parameter and no output schema, the description does list the expected return metrics (cost basis, average cost per oz, break-even price, unrealized P/L per metal) and notes 'per metal' grouping. Yet it omits the response shape, whether it shows all metals or requires filters, and any usage context, leaving it adequate but sparse.

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 schema has 100% coverage for the single api_key parameter with a clear description, so the baseline is 3. The description does not add any additional parameter meaning beyond what the schema already states.

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 lists specific analytics metrics (cost basis, average cost per oz, break-even price, unrealized P/L per metal) which clearly indicates the tool's function, and it distinguishes itself from siblings like get_portfolio and get_speculation by focusing on these valuation metrics. However, it lacks an explicit verb, relying on the title 'Get Portfolio Analytics' to convey the action.

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 guidance on when to use this tool versus alternatives such as get_portfolio or get_daily_brief. No context, prerequisites, or exclusions are provided, leaving the agent to infer usage solely from the metric list.

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