Discover Devices

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

With no annotations, the description carries the burden. It discloses the side effect of feature learning ('By default, the tool also learns the commands available on discovered devices') and explains networkPrefix behavior. However, it stops short of detailing network impact or permission requirements, so it's not fully rich but is solid.

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 three sentences: purpose, usage scenarios, and key behavioral toggle. Every sentence earns its place, concise and well-structured.

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 an 11-parameter tool with no output schema, the description covers the critical decisions (when to use, networkPrefix, refreshFeatures) while other parameters are well documented in the schema. Missing return-value details but adequate for selection and invocation.

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 100%, so the baseline is 3. The description adds meaning to key parameters by explaining that omitting networkPrefix scans the active local network and setting refreshFeatures to false avoids feature learning. This goes beyond the schema's literal field descriptions.

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: 'Find live micrOS devices on a local IPv4 /24 network.' It uses a specific verb and resource, and the mention of device discovery distinguishes it from siblings like list_devices and search_devices.

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?

Explicit usage guidance is provided: 'Use this during initial setup, when a device is missing from list_devices, or when its IP address may have changed.' It also contrasts with list_devices and gives a when-not for refreshFeatures, offering clear contextual direction.

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