unified_probe_backend

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

States the operation is safe and read-only, but no details on what the diagnostic entails, potential results, or side effects. Since no annotations exist, the description carries the full burden and is insufficient.

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?

Extremely concise and to the point. Includes essential information (safe, read-only, backend choices) without redundancy or unnecessary words.

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?

Given the absence of an output schema and annotations, the description lacks details about what the diagnostic returns or accomplishes. It's vague about the nature of the probe, leaving the agent uncertain about outcomes.

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 only parameter 'backend' is well-defined via enum and required, providing full schema coverage. The description adds minimal value beyond restating the options, so it meets the baseline.

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?

Clearly states the tool runs a safe read-only diagnostic and specifies the backend options (plumb or custom). Distinguishes from sibling tools like unified_status or unified_backends by focusing on probing a backend.

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?

Provides a hint of usage ('diagnostic', 'safe read-only') but lacks explicit guidance on when to choose this tool over alternatives. No mention of conditions or context for probing.

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