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

With no annotations provided, the description bears the full burden of behavioral disclosure. It indicates a read operation by listing return values, but does not explicitly state that it is read-only, nor does it mention authentication requirements, rate limits, or error behavior. The description adds some context about the return payload but lacks deeper transparency.

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 front-loads the primary action and efficiently lists the key data components. Every word contributes meaning, with no filler or 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?

For a simple getter with one parameter and no output schema, the description adequately covers the return values and scopes the tool's purpose. It might have mentioned authentication behavior or error handling, but these are not critical given the simple nature and schema coverage. Overall, the description is sufficiently complete for a portfolio retrieval 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 fully documents the only parameter (api_key) with a description 'TroyStack API key (required)', achieving 100% schema description coverage. The tool description adds no additional parameter-specific information, so the baseline score of 3 applies.

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's function with a specific verb ('Returns') and a specific resource ('precious metals portfolio'), enumerating the exact data components (total value, cost basis, gain/loss, per-metal breakdown, individual holdings). It is easily distinguished from sibling tools like get_spot_prices or get_analytics, which target different data domains.

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 implies when to use the tool—whenever an agent needs portfolio information—but does not explicitly state usage context, exclusions, or alternatives. There is no mention of when not to use it or which sibling tool might be more appropriate for related queries. This is implied usage rather than explicit guidance.

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