mdns_unregister_service

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

The description adds context that the tool removes and stops advertisement, aligning with the destructiveHint annotation. However, it does not elaborate on potential side effects, error conditions, or permission requirements beyond what annotations already convey.

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 well-structured with sections for purpose, arguments, returns, and an example. It is concise, though the Args section repeats information already present in the input schema.

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 parameter, the description covers purpose, usage, parameter details, return value, and provides an example. It is contextually complete given the tool's low complexity and the presence of annotations.

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?

With schema description coverage at 0%, the description compensates by explicitly listing the parameter (service_name) with type and a clear example. This adds meaningful semantic value beyond the schema's minimal description.

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 uses a specific verb 'unregister' and identifies the resource as 'mDNS service', clearly distinguishing it from sibling tools like mdns_register_service (opposite) and mdns_browse_services (browsing). It explains the effect of removing the service and stopping its advertisement.

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 description implies usage for removing previously registered services, which is a clear context. However, it does not explicitly state when not to use the tool or provide alternatives, but the sibling tool names are available for context.

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