list_connected_probes

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

No annotations are provided, so the description carries the burden. It states a read-only listing operation, but does not explicitly mention side-effect-free behavior or any prerequisites. For a simple list operation, this is adequate but not rich in behavioral disclosure.

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 description is just two short sentences with no wasted words. Each sentence adds value: the first states the action and scope, the second gives usage guidance.

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?

For a zero-parameter, no-output-schema discovery tool, the description is functionally complete. It states what is listed, the scope, and when to use it, and the sibling context confirms this is a simple enumeration tool.

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 schema has zero parameters, and the description correctly requires none. Baseline 4 applies for zero-parameter tools; the description adds no parameter-specific details because there are none to explain.

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 uses a specific verb 'List' with resource 'probes' and scope 'currently connected to this machine,' clearly distinguishing it from sibling tools like probe_connect or configure_probe. The phrase 'Start here if unsure what probe to use' further establishes its role as the initial discovery tool.

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?

The description explicitly says 'Start here if unsure what probe to use,' giving clear when-to-use guidance and positioning this tool as the entry point for probe selection. It doesn't name specific alternatives or exclusions, but the context is clear and sufficient for a discovery tool.

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