Book Lightyear Trades

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

The description adds the important behavioral trait 'DRY RUN by default' and the requirement for capital_gains_file on sells. This complements the annotations (destructiveHint=true) by clarifying that actual booking only occurs when dry_run is false. However, it doesn't detail the booking process or side effects.

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?

Three concise sentences, each carrying essential information: purpose, default behavior, and a key requirement. 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 tool's complexity (11 parameters, destructive, no output schema), the description covers the core function but lacks information about return values or outcomes. It does not explain what happens after successful booking (e.g., created transactions). The absence of output schema output increases the need for such info.

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 schema already describes all 11 parameters with 100% coverage. The description reinforces the dry_run default and the capital_gains_file requirement for sells, adding minimal extra meaning beyond the schema.

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 it books Lightyear stock Buy/Sell trades, specifying the asset type (stock) and operation (buy/sell). This distinguishes it from siblings like book_lightyear_distributions and parse_lightyear_statement.

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?

It mentions that for sells, capital_gains_file is required, but does not explicitly state when to use this tool versus alternatives (e.g., book_lightyear_distributions). The dry run default is noted, but no exclusions or prerequisites are given.

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