portfolio_compare_tickers

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

No annotations are provided, so the description carries full burden. It discloses what metrics are compared but does not mention side effects, permissions, or whether it is read-only. The tool likely does not modify data, but that is not stated, limiting 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?

Description is concise and well-structured with bullet points, making it easy to scan. Every sentence adds information. No 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?

Given the output schema exists, the description focuses on input and behavior. It covers all key aspects: what is compared, the metrics, and the portfolio fallback. No gaps identified.

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?

All 4 parameters have schema descriptions (100% coverage). The description reinforces the behavior of the tickers parameter (null uses portfolio). This adds some value, but the schema already conveys this information.

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 compares multiple tickers using technical and fundamental metrics, and lists specific categories (price performance, RSI, etc.). It distinguishes from siblings like compare_tickers by highlighting portfolio integration.

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?

Provides clear guidance: if no tickers provided, automatically uses portfolio holdings. This tells the agent when to use it (for portfolio overview or specific ticker comparisons). However, it does not explicitly mention when not to use it or name alternative tools.

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