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

No annotations are provided, so the description carries the full behavioral burden. It discloses an authentication requirement ('InsideREU API key') and some return fields, and 'List' implies a read-only operation. It does not clarify pagination, rate limits, or whether any side effects occur, leaving meaningful gaps for a no-annotation tool.

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 two short sentences with no waste. The primary listing behavior is front-loaded, and the authentication constraint follows directly, making it easy to scan.

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 one-parameter list tool with no output schema, the description gives the core purpose, an auth requirement, and a summary of returned fields. It could say more about ordering or pagination, but it is largely sufficient for correct invocation.

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?

Schema description coverage is 100%, so the single optional 'status' enum parameter is already fully documented in the schema. The description adds no parameter-specific meaning such as what 'open', 'closed', or 'all' return, so the baseline 3 is appropriate.

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 states a specific verb ('List') and resource ('YOUR tracked trades'), and it names several returned fields. It is clearly distinguishable from sibling mutation tools like track_trade and close_trade, but it does not explicitly contrast itself with any alternative, keeping it below a 5.

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?

Usage is implied by 'List YOUR tracked trades' and the prerequisite 'Requires an InsideREU API key' is useful. However, there is no explicit guidance on when to use this tool versus siblings such as track_trade or get_track_record_ten, nor any exclusions or conditions.

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