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

No annotations are provided, so the description carries the entire burden of behavioral disclosure — and it supplies none. It does not say whether this is a read-only diagnostic, what inputs it consumes versus internally derives, whether it requires a live SDK/room context, or what it returns; the parameter names (hasSocket, validated, hasRoomName) hint at a state-probing operation but the description never confirms or explains this.

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?

It is short, but brevity here comes from under-specification rather than efficient writing: the entire body is a repeated identifier and a redundant gloss. There is no front-loaded statement of purpose because no purpose statement exists.

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 six mostly undocumented parameters, no output schema, no annotations, and a name-echo description, an agent cannot determine what a 'readiness diagnostic' is, what inputs it should supply, or what it will receive back. This is entirely inadequate for the tool's apparent complexity.

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?

Six parameters exist with only 17% schema description coverage, so the description must compensate — it explains nothing. It does not clarify whether hasSocket/hasLocalSocket/validated/hasRoomName are caller-supplied flags or diagnostic outputs, nor what failureMessage or participantCount contribute to a readiness verdict.

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 is a namespace-qualified restatement of the tool name plus the parenthetical tag 'readiness-diagnostic', which merely rephrases 'readiness.diagnose'. It names no verb, resource, or outcome an agent could act on, and it does nothing to distinguish this tool from the many sibling 'runtime.diagnose' variants across platforms.

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?

There is no guidance whatsoever on when to use this tool, when not to, or how it relates to alternatives such as shared::runtime.diagnose or any of the platform-specific runtime.diagnose siblings. The agent is left to guess from the name alone.

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