homescan_discover

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the action (discover devices via ARP table) and return data, but does not cover aspects like performance (e.g., speed, network impact), error handling, or prerequisites (e.g., network permissions). It adds basic context but lacks depth for a tool with potential network interactions.

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, consisting of two sentences that efficiently convey the tool's purpose and return data. Every sentence adds value without redundancy, making it easy to understand quickly.

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 tool's moderate complexity (network discovery with one parameter) and no annotations or output schema, the description is adequate but incomplete. It covers the core functionality and return data but lacks details on behavioral traits (e.g., network impact, error cases) and does not explain the output format beyond a high-level list, which could be insufficient for an agent to handle results effectively.

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 description coverage is 100%, so the schema fully documents the single parameter 'refresh'. The description does not add parameter-specific details beyond what the schema provides, but with only one optional parameter, the baseline is high. It implicitly supports the parameter by mentioning the ARP cache and ping sweep in the context of discovery.

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 purpose with specific verbs ('discover all devices') and resources ('local network using ARP table'), and distinguishes it from siblings by specifying the discovery method and return data (IP, MAC, manufacturer). It goes beyond a tautology of the name 'homescan_discover' by explaining the action and scope.

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 implies usage for network device discovery but does not explicitly state when to use this tool versus alternatives like 'homescan_diff' or 'homescan_flagged'. It provides some context (local network, ARP-based) but lacks explicit guidance on exclusions or comparisons with sibling tools.

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