store_trade_lesson

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

Annotations indicate idempotence and non-destructiveness, but the description does not provide additional behavioral context, such as whether lessons can be overwritten or if there are storage limits. No contradictions with annotations.

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 concise sentences plus a required-fields note, front-loading the purpose with no 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?

Given the 50% schema coverage and no output schema, the description covers purpose and required params but omits details on optional parameters, duplicate handling, and post-storage behavior.

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 description highlights required fields (symbol, direction, outcome, lesson) but adds minimal value beyond the schema for optional parameters pnl and regime, which have low schema coverage. Baseline 3 due to 50% coverage.

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 persists a trade lesson for autonomous learning, specifying the action and purpose. However, it does not differentiate from the sibling tool 'capture_learning_signal', which likely has a similar function.

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 lists required fields and implies usage when storing a trade lesson for future learning, but lacks explicit guidance on when not to use or alternatives, such as 'capture_learning_signal'.

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