connect_websocket

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

Discloses connection and wait with timeout (up to 25s). Lacks details on idempotency, error handling, or what 'registered' means. Without annotations, more behavioral context would be beneficial.

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, front-loaded with action and constraint. 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?

Covers purpose and usage prerequisite. Missing return value or error scenario details, but simple tool with one parameter and clear context from sibling tools is adequately described.

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?

Only parameter 'wallet_address' has no schema description. Description mentions 'for a wallet' but doesn't specify format or constraints. Schema coverage is 0%, so description partially compensates.

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 connects a websocket for a wallet and waits for registration, with a specific timeout. It also explicitly says 'Call before placing orders,' distinguishing it from order placement siblings.

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?

Explicitly says 'Call before placing orders,' providing clear when-to-use guidance. Does not mention alternatives or when not to use, but the context implies it's a prerequisite.

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