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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuine behavioral content beyond that: that reconnect/replay semantics exist, that execution.report is a wallet-scoped auto-delivered channel, and that webhooks are the async fallback path. It does not contradict the annotations in any way.

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?

A single front-loaded sentence leads with the primary subject (the WebSocket transport) before the secondary topics, and no clause is filler. The dense parenthetical stacking ('URL, auth schemes, message shapes, reconnect/replay protocol') makes it slightly harder to scan than a short bulleted opener, but it stays within one sentence.

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?

With zero parameters and an output schema present, the description need not explain return values, and its enumeration of covered topics is sufficient to decide whether to call it. The one remaining gap is that it does not clarify how this tool divides work with the closely named problee_discover_webhooks sibling, which would matter for an agent choosing between the two.

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 takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. No parameter claims are made that could mislead.

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 names a specific deliverable (the Agent WebSocket transport spec) and enumerates its contents: URL, auth schemes, message shapes, reconnect/replay protocol, plus the WS↔webhook taxonomy bridge and wallet-scoped execution.report channels. That is far more concrete than a bare 'describe' verb. It stops short of distinguishing itself from sibling problee_discover_webhooks, whose subject matter it partly overlaps.

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?

Usage is implied rather than stated: an agent can infer it should call this to learn the streaming transport before integrating, and the phrase 'webhooks as the async fallback' hints at the relationship to the webhook path. There is no explicit when-to-use / when-not-to-use rule and no named alternative (problee_discover_webhooks, problee_list_capabilities) that an agent should pick instead.

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