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

No annotations are present, so the description carries the behavioral burden. 'List' signals a read operation, and 'availability for YOUR connected exchange keys' signals that results are key-dependent. However, it does not state what happens when no keys are connected, whether external calls are made, or any failure/rate-limit behavior.

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 one dense, front-loaded sentence that states the action and resource immediately and supports it with concrete exchange examples. The final clause is slightly redundant with the availability point made earlier, but the overall length is reasonable and every piece of information earns its place.

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 parameterless listing tool with no output schema, the description adequately explains what the agent receives: a list of aggregated exchange MCP servers and skill libraries with availability for its connected keys. It does not detail the exact response format, but the use case is simple enough that this is not a critical omission.

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 schema already covers 100% of parameter documentation, so the description has no obligation to explain arguments. The output-oriented phrase 'tells an AI client which exchange skills it can actually use' adds useful context without conflicting with the empty schema.

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 begins with the verb 'List' and names a specific resource: official exchange MCP servers and AI skill libraries, with concrete examples (Binance, BingX, OKX, Bybit, Coinbase). It also clarifies the key differentiator—availability filtered for the caller's connected keys—so an agent can distinguish it from other list-style sibling tools, though it does not name a sibling explicitly.

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 clearly implies when to use the tool: when an AI client needs to discover which exchange skills are actually usable with its connected keys. It gives specific context but does not mention alternatives or exclusions, so it stops short of full explicit routing guidance.

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