moomoo_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. 'Get' implies a read-only, non-destructive operation, and the symbol format constraint sets input expectations. However, it doesn't disclose rate limits, error behavior, or what exactly constitutes a snapshot.

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 concise sentences with the action verb front-loaded and the constraint following. No filler, repetition, or unnecessary detail.

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?

For a one-parameter snapshot tool, the description covers the essential action and input format, and an output schema exists. However, it omits usage context relative to siblings and any details about what a snapshot includes or error conditions, leaving some ambiguity for an agent deciding between this and moomoo_quote/candles/ticker.

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 has 0% description coverage, so the description is the sole source of parameter meaning. It adds concrete format examples ('US.AAPL', 'HK.00700') clarifying that codes must be prefixed with a market code. It doesn't enumerate all accepted market prefixes or explain array semantics, but it provides a solid baseline.

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 states a clear verb and resource: 'Get market snapshots.' This is specific enough to identify the core action. However, it doesn't differentiate from siblings like moomoo_quote or moomoo_ticker, which could also return market data.

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?

No guidance is given on when to use this tool versus the sibling tools. The only additional instruction is the symbol format requirement, which is a parameter constraint rather than usage context. There is no mention of alternatives or exclusions.

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