discover_printers

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

Describes scanning method, timeout parameter, and return value summary. No annotations provided, so description carries full burden. Could mention safety (read-only) or network impact.

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?

Concise and well-structured: purpose first, then method details, then Args/Returns. Every sentence adds value with no waste.

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?

Covers purpose, method, parameter, and return value adequately for a simple discovery tool. Could optionally mention network requirements or errors, but not essential.

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?

Only one parameter (timeout) with clear explanation 'Maximum scan duration in seconds (default 5)'. Schema coverage is 0%, so description adds needed semantic value beyond schema title.

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?

Clearly states 'Scan the local network for 3D printers' with specific methods (mDNS/Bonjour, HTTP subnet probing) and lists supported printer types. Distinct from sibling tools like register_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?

Explicitly tells to use register_printer for adding discovered printers. Provides clear context for when to use (network discovery) but lacks explicit when-not examples.

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