Get Trade Reflection

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the agent knows this is a safe, repeatable local read. The description adds only that the content covers 'reasoning and lessons,' a small increment beyond the structured hints and output schema.

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 short sentences, no filler, with the core action front-loaded in the first sentence. Marginally wasteful in that the second sentence largely restates the first's intent rather than adding new information.

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?

An output schema exists so return values need not be described, the single required parameter is fully covered, and annotations carry the safety profile. The definition is sufficient to invoke the tool, though it stops short of routing guidance among overlapping trade/memory siblings.

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% and the single trade_id parameter is already documented in the schema as 'The trade ID to look up.' The description adds no syntax, format, or lookup semantics beyond that, so the baseline of 3 applies.

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 specific verb+resource ('Get the full context and reflection for a specific trade'), so the agent knows exactly what is retrieved. However, it does not distinguish this tool from memory/analysis siblings like recall_memories or get_behavioral_analysis, which could plausibly surface trade reasoning.

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?

'Use this to deep-dive into a particular trade's reasoning and lessons' gives an implied context for use but names no alternatives, exclusions, or prerequisites. With several overlapping trade/memory tools in the sibling list, explicit routing guidance is missing.

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