ws_snapshot_summary

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

No annotations are provided, and the description only implies a read operation ('Get') with no mention of safety, destructiveness, authentication requirements, rate limits, or other behavioral traits. The phrase '24h summary snapshots for all pairs via WebSocket' adds purpose context but not behavioral 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?

One concise sentence of 10 words, front-loaded with the action verb. Every word is informative, and there is no redundancy or unnecessary detail. It is appropriately sized for the tool's simplicity.

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 simplicity (no parameters, no output schema, no annotations), the description provides the essential purpose and scope. However, it does not mention whether this is a subscription or a one-time request, nor does it hint at the response format or behavior. Slightly incomplete for a tool with no output schema.

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 tool has zero parameters, and the input schema is an empty object (100% coverage trivially). The description adds value by stating 'for all pairs', indicating no filtering is possible, which aligns with the schema. Baseline for no parameters is 4, and the description meets it.

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 retrieves 24h summary snapshots for all pairs via WebSocket, specifying the verb 'Get', the resource '24h summary snapshots', the scope 'all pairs', and the method 'WebSocket'. This effectively distinguishes it from sibling tools like ws_snapshot_book and ws_snapshot_ticker, which focus on book and ticker snapshots respectively.

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 explicit guidance on when to use this tool versus alternatives like ws_snapshot_book, ws_snapshot_ticker, summaries, or ticker_all. The description only mentions 'via WebSocket' indicating a streaming context, but lacks directives on prerequisites, when not to use, or how it differs from REST-based summaries.

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