mdns_get_service_info

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

Annotations already indicate readOnlyHint, idempotentHint, destructiveHint=false. Description adds context that it retrieves 'complete information' with specific fields. No contradictions. Could mention network/timeout behavior but annotations cover safety.

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?

Description is well-structured with purpose first, then details, then args, then example. Slightly verbose with full Args section and example, but every part adds value. Could be trimmed but still good.

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 read tool, description covers input parameters, return value (string with markdown example), and usage example. Annotations provide safety profile. Output schema not in input but described in text. Fairly complete given tool complexity.

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 provides full descriptions for all parameters (service_type, service_name, timeout, response_format). Description includes a clear 'Args' section that restates and slightly augments (e.g., default timeout 10.0). Adds value by summarizing parameter purpose beyond schema, even though schema coverage is high.

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?

Description clearly states 'Get detailed information about a specific mDNS service' and lists specific data items (hostname, IP, port, TXT records). Distinguishes from sibling tools like mdns_browse_services (listing) and mdns_register_service (write operation).

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?

Description implies use after browsing (service name from browse results) but does not explicitly state when to use vs alternatives or when not to. No exclusions or alternative tool mentions. Usage context is implied but not explicit.

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