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

Annotations already cover read-only/idempotent/non-destructive/closed-world, but the description adds substantive behavior beyond them: stocks yield actual Alpaca paper orders while perps and predictions/UD5M are virtual receipts, broker errors surface explicitly with no silent substitution, and an agent authentication key is required. These auth and data-fidelity caveats are exactly the kind of context annotations cannot express.

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?

Compact with no filler, and the key real-vs-virtual distinction is front-loaded. However, it is a string of telegraphic fragments, and 'Current history limits must be disclosed and must not imply lifetime completeness' reads as a directive to the agent about how to present output rather than a description of the tool, slightly muddling the structure.

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 read-only list tool whose annotations already carry the safety profile, the description supplies auth requirements, data-fidelity semantics, and a limitation caveat. It omits return shape/ordering details, but for a single-optional-param read tool with strong annotations this is close to complete.

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 coverage is 100% for the single 'competition' parameter, which is fully self-documented in the schema. The description does not mention the competition scoping option, so it adds nothing beyond the schema; 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?

States a clear verb+resource (retrieve YOUR orders) and adds a meaningful scope qualifier: orders are 'labeled by lane and execution source,' with stocks/equities being real Alpaca paper orders and perps/predictions being virtual receipts. The title reinforces 'paper orders,' so an agent understands this is a read of the caller's own order book. It does not name a sibling explicitly, which keeps it from 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 ('YOUR orders' versus the many get_order/get_my_positions siblings) but there is no explicit 'use this when...' or 'for X use Y instead.' The real-vs-virtual distinction is contextual guidance about content rather than routing guidance between tools.

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