get_snapshot

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns structure, liquidity, FVGs, and order blocks, but it does not discuss any behavioral traits such as read-only nature, performance, or how 'nearest' or 'unfilled' are determined. The description is adequate but lacks depth.

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 a single sentence that is concise and front-loaded with the key concept 'One-call snapshot'. However, it could be slightly more detailed without losing conciseness, such as clarifying the parameters.

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 complexity of the tool (aggregating three concepts) and the existence of an output schema, the description is partially complete but fails to explain the decision criteria for the aggregated elements (e.g., what 'nearest' means) and leaves parameter semantics entirely undeclared.

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 description coverage is 0%, and the description provides no explanation of the parameters (symbol, limit, timeframe) beyond their names. The agent must infer their meaning, which is insufficient for correct invocation.

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 provides a 'snapshot' combining market structure, nearest liquidity, unfilled FVGs, and recent order blocks, which differentiates it from sibling tools that focus on individual components. The verb 'snapshot' implies a composite view, making the resource and action specific.

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 for a quick overview of multiple market concepts in one call, but it does not explicitly state when to use this tool versus the more specific siblings, nor does it provide when-not scenarios or alternatives.

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