Find TEPRA printers

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

With no annotations, the description is the sole source of transparency. It reveals the network method (mDNS) and result (IP addresses), which is helpful. However, it does not disclose edge cases like no printers found, timeout behavior, or read-only nature. More detail would be beneficial.

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, well-structured sentence with no filler. It is front-loaded with the action and target, making it efficient and easy to parse.

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 a simple tool with one optional parameter and no output schema, the description covers the primary behavior and return type (IP addresses). It does not explicitly state empty-result behavior or the exact return format, but the core use case is clear. Slightly more detail would make it fully complete.

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% (timeoutMs is described in the schema), so the description needs no additional parameter information. It does not add value beyond the schema, hence the baseline score of 3.

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 states a specific action ('Search') with a clear target ('TEPRA printers on local network'), method ('mDNS'), and outcome ('return their IP addresses'). This clearly distinguishes it from sibling tools that operate on an already-discovered printer.

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?

Usage is implied by the purpose—use when you need to discover printer IPs—but the description does not explicitly state when to use this tool vs alternatives or mention prerequisites. No reference to siblings or a typical workflow is provided.

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