get_trade_reflection

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'get' and 'deep-dive,' which imply a read-only operation, but does not specify permissions, rate limits, error handling, or what 'full context and reflection' entails in terms of data format or depth. This leaves significant gaps for a tool with no annotation coverage.

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 appropriately sized and front-loaded: the first sentence states the core purpose, the second provides usage context, and the 'Args' section efficiently documents the parameter. Every sentence adds value without redundancy, making it concise and well-structured.

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 (single parameter, read-focused) and the presence of an output schema (which handles return values), the description is largely complete. It covers purpose, usage, and parameter semantics. However, it lacks behavioral details like permissions or error handling, which are important since no annotations are provided, preventing a score of 5.

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 includes an 'Args' section that explains the single parameter 'trade_id' as 'The trade ID to look up,' adding meaning beyond the input schema, which has 0% description coverage. Since there is only one parameter and the description clarifies its purpose, it compensates well for the low schema coverage, though it could provide more details like format or examples.

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's purpose: 'Get the full context and reflection for a specific trade' and 'deep-dive into a particular trade's reasoning and lessons.' This specifies the verb ('get'), resource ('trade'), and scope ('context and reflection'), but it does not explicitly differentiate it from sibling tools like 'recall_similar_trades' or 'remember_trade,' which prevents a score of 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?

The description implies usage context by stating 'Use this to deep-dive into a particular trade's reasoning and lessons,' suggesting it's for detailed analysis of a single trade. However, it does not provide explicit guidance on when to use this tool versus alternatives like 'recall_similar_trades' or 'get_strategy_performance,' nor does it specify any exclusions or prerequisites.

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