mDNS Service Discovery

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It only states the basic function (discovery) without detailing network traffic, permissions needed, side effects, or performance implications. This is insufficient for safe and effective agent use.

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 extremely concise, consisting of two sentences with no extraneous information. Every word contributes to conveying the tool's purpose.

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 tool has one optional parameter and no output schema. The description does not mention what the tool returns (e.g., list of service names/addresses), error handling, or behavior when no services are found. Given the simplicity, more detail is needed for an agent to use it reliably.

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 description coverage is 0%, so the description must explain the 'serviceType' parameter. The description lists examples (HTTP, HTTPS, MCP) but does not explicitly state that the parameter controls the service type filter, nor does it clarify valid values or format. The 'default' of 'http' is not noted.

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 action (discover services) and the technology (mDNS/Bonjour) with concrete examples (HTTP, HTTPS, MCP servers). It distinguishes well from unrelated sibling tools like text_analysis, word_count, and key_value_store.

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?

No guidance on when to use this tool or when not to. There is no mention of prerequisites, alternatives, or context such as network requirements. The description implies use cases but lacks explicit direction.

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