rp_connection_probe

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

Annotations already cover safety and idempotency, but the description adds two things they do not: the operation briefly consumes a server accept slot (a real side effect on the remote side) and a successful connect is not proof of identity. Those are meaningful operational caveats beyond readOnlyHint/idempotentHint. It still says nothing about timeouts or failure modes.

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 dense clauses, no filler, with the action front-loaded ahead of the caveats. Every phrase carries information; even the terse 'no selector' is at least positioned as a qualifier rather than padding.

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?

An output schema exists, so return values need no explanation, and the 'no identity proof' note is a useful interpretation caveat. However, with zero parameters it is unexplained what host/port the probe targets (presumably configured elsewhere) and how long it waits before failing, which matters for an agent interpreting a negative result.

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 no parameter semantics to explain; baseline 4 applies. One could argue the description should explain where the connect target comes from, but that is a completeness rather than a parameter-documentation issue.

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?

It does name a concrete action (open and close a TCP connection) rather than restating the name, but 'with no selector' is unexplained jargon and the phrase 'connection_probe' is never plainly glossed as 'check that the server accepts TCP connections.' Nothing distinguishes it from siblings like rp_rx_connect or rp_connection_status, so an agent must infer the difference.

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 statement of when this tool should be chosen over rp_rx_connect, rp_connection_status, or rp_device_diagnostics. The only hint at appropriate use is the implicit 'no identity proof' caveat, which tells an agent what it cannot conclude but not when to run it.

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