remote_test

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and network scope are covered. The description adds that a harmless marker command is executed, confirming the probe is non-destructive, but says nothing about authentication requirements, timeouts, or what constitutes success versus failure on an unreachable host.

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 purpose is front-loaded in one sentence and the SSL guidance follows as secondary detail with no filler. The line break mid-sentence is cosmetic; overall it is tight and earns its length.

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?

Error behavior on failure and the exact nature of the marker command are not spelled out, but for a diagnostic probe with an output schema and safety annotations this is a minor omission. An agent has enough to select and call it correctly, including the tricky SSL/cert cases.

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?

Schema coverage is 0%, so the description carries the load. "Saved or ad-hoc" implicitly maps to the profile and connection parameters, and the SSL notes document nested connection fields (ssl, cert_validation) that the schema leaves entirely bare, but the top-level parameters are never named or described, leaving a real gap at 0% coverage.

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?

Uses a specific verb ("Test") on a specific resource ("a saved or ad-hoc connection") and distinguishes the two connection modes (profile vs. inline connection). It doesn't name any sibling tool or explain where this fits relative to remote_execute or remote_session_open, so an agent must infer the routing.

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 only implied: you call it to verify a connection before doing real work. The SSL paragraph does give conditional guidance (port 5986 -> ssl=true, self-signed -> cert_validation=false, ssl=false means plain HTTP not disabled verification), which is genuinely useful, but there are no exclusions, prerequisites, or alternatives named.

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