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

Beyond the annotations, it discloses the data source (public IEEE registry), the returned artifacts (maker, likely device type, private/randomized and camera/smart-home flags, next steps, router-specific instructions), and the key behavioral boundary that it never scans or connects to a network and works only from user-supplied input. This adds real context on top of readOnlyHint/idempotentHint rather than restating them.

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?

It is front-loaded with the usage trigger, then parameters, then return values, then exclusions — a sensible order for routing. It is a dense block, and the six-character MAC rule is stated twice (in prose and again via the schema), so there is minor redundancy, but nearly every clause carries actionable information.

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?

With no output schema, the description fully carries the burden of explaining what comes back, and it does so concretely. Combined with explicit scope exclusions and complete parameter guidance, an agent has everything needed to decide and call correctly.

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 earns slightly more by tying parameter shapes to workflows — one entry for a single lookup, an empty list plus optional brand to get instructions for finding the list. Some of the MAC-prefix detail (only first 6 characters used, IP unnecessary) duplicates the schema's own field descriptions, so it is reinforcement rather than new meaning.

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 opens with a concrete trigger set ("who is on my wifi", unknown device, MAC vendor lookup) and a specific resource: identifying devices from a pasted router list via MAC prefix. It is plainly distinguishable from the sibling tools because it explicitly rules out scanning, locating, or monitoring, leaving this as the identification/vendor-lookup 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?

It gives explicit when-to-use phrasing tied to real user utterances, plus a clear when-not-to-use list (do not scan a network, find a person or location, monitor someone, or access another person's network). It also routes sub-cases: single lookup → one entry, no list yet → empty list plus router brand.

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