scan_devices

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

No annotations are provided, so the description carries the full burden. It says the tool scans devices but does not disclose whether the operation is read-only, whether it triggers pairing, or any side effects or permissions needed. The phrase 'include_unpaired para emparejar nuevos' hints at purpose but does not clarify behavioral impact.

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 concise and front-loaded, stating the main purpose first. It includes only two sentences and no filler. However, it is perhaps too terse to convey sufficient detail.

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 description is minimal for a tool with one optional parameter and a rich sibling set. It doesn't differentiate from list_devices or explain prerequisites or behavior. The output schema exists, so return value details are covered, but usage context is lacking. Given the tool's simplicity, it's adequate but has clear gaps.

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 0% description coverage, so the description must explain the parameter. It states that include_unpaired is for pairing new devices, which adds meaning beyond the schema's title. However, the explanation is terse and doesn't clearly state that unpaired devices are included in the scan results or what false means.

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 scans KDE Connect devices, using a specific verb and resource. It also mentions the include_unpaired parameter's purpose, which adds context. However, it does not explicitly differentiate this from the sibling list_devices, so it is clear but lacks sibling differentiation.

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 guidance on when to use scan_devices versus list_devices or any other siblings. The description only implies that include_unpaired is for pairing new devices, but doesn't state when to choose this tool over alternatives.

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