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

With no annotations, the description must carry behavioral disclosure. It does add two useful traits beyond the name: the lookup is offline/local and the result includes local/multicast bits. It does not disclose input format expectations or table limitations, but for a read-only lookup that is a moderate disclosure.

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 compact sentence with no filler, front-loading the core purpose. It earns its place, though it is so terse that it sacrifices useful 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 leaves out the crucial input-side semantics: what q should contain and in what format. Given one parameter, no annotations, and an output schema that presumably covers return values, this omission makes the definition incomplete for reliable invocation. The offline/local note helps but is not enough.

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 one parameter (q) with 0% description coverage, and the description never mentions q or what format it expects. The agent must guess that q is a MAC address and what separators are accepted. The tool description does nothing to compensate for the missing schema documentation.

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 identifies the tool as a MAC vendor (OUI) lookup, specifying it resolves the vendor and local/multicast bits from a local, offline OUI table. This is clear resource+scope, though it lacks an explicit verb and does not name sibling tools like macvendorlookup or macvalid, so some differentiation is left to inference.

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 phrase 'local OUI table (offline)' implies the tool is meant for offline lookups, giving some context for when to choose it. However, it never states when not to use it or how it compares with siblings such as macvendorlookup, leaving the routing decision to inference.

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