ws_snapshot_ticker

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 mentions 'real-time price snapshot via WebSocket' but does not clarify whether this is a one-time request or a subscription, nor does it disclose connection management, auth requirements, or rate limits. The behavior is ambiguous.

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 concise sentence that front-loads the key purpose and speed advantage. No unnecessary words.

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 simple single-parameter nature and no output schema, the description is adequate but falls short on explaining WebSocket-specific behavior (e.g., connection lifecycle, return format). More detail would improve agent decision-making.

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 100% with an example for the 'pair' parameter. The description does not add new information beyond the schema, achieving the baseline score.

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 verb 'Get', the resource 'price snapshot', and the distinguishing method 'via WebSocket (faster than REST)'. It effectively differentiates from siblings like 'ticker' (likely REST) and 'ws_snapshot_book'/'ws_snapshot_summary' (other WebSocket snapshots).

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 using WebSocket for speed advantage but lacks explicit guidance on when to use this tool vs alternatives like 'ticker' or when to avoid it. It does not provide context for selection among sibling WebSocket snapshot tools.

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