get_realized_gains

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

Discloses the method (FIFO) and transaction type (SELL). As a read-only operation with no annotations, the description adds useful behavioral context beyond the name, though it does not mention output format or edge cases.

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 concise sentences that front-load the purpose and add access restrictions without any wasted 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?

Covers the core function, method, and access requirements. Missing output format description, but otherwise complete for a simple get tool with no parameters.

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, so the description does not need to explain them. Baseline score of 4 applies, as the description does not detract.

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?

Clearly states it retrieves realized gains from SELL transactions using FIFO cost basis, distinguishing it from sibling tools like get_cost_basis. The verb (Get) and resource (realized gains) are specific.

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?

Mentions premium gating and API key requirement, providing context for when it can be used. However, it does not explicitly differentiate from alternatives like get_cost_basis or state when not to use it.

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