list_connected_devices

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

With no annotations, the description carries the full burden of disclosing behavior. It clearly indicates the output contents (port address, driver name, mode) and that it is a read-only listing operation. While it doesn't describe side effects, the word 'List' makes it clear this is non-destructive.

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 a single, concise sentence that includes all essential information without waste. It is front-loaded with the primary action and includes the needed details.

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?

The tool is simple with no parameters, and an output schema exists. The description additionally clarifies the content of the output (port address, driver name, mode), which is helpful. It fully addresses what the agent needs to know for this simple listing operation.

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 has zero parameters, so the description does not need to explain parameters. The baseline score of 4 applies, and the description appropriately focuses on the return information.

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 clearly states the tool's function: listing motors and sensors connected to the EV3, with specific details (port address, driver name, mode for sensors). This is a specific verb + resource and distinguishes itself from sibling action-oriented tools like move_forward or beep.

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 implicitly suggests using this tool when you need to know which devices are connected, but it does not explicitly mention when to use it over alternatives or provide exclusions. No sibling tool overlaps directly, but the lack of explicit guidance lowers the score.

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