network_status

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds that the tool performs an internet test and returns a summary string, which is useful but not deeply detailed about external network behavior or potential failures.

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 short and front-loaded with the core network-diagnostics scope. The Args/Returns section is somewhat redundant with the schema but stays compact and readable.

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-only status tool, the description is mostly complete: it enumerates what is checked, mentions a return type, and is supported by schema details for host and response_format plus annotations. It could be more complete with explicit usage guidance, but nothing critical is missing for invocation.

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?

The description merely restates the parameter names 'host, response_format' without adding meaning. With schema description coverage reported as 0%, the description does not compensate by explaining defaults, remote-host requirements, or response-format choices.

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 identifies the resource: network interfaces, IP addresses, default gateway, DNS, and an internet test. It lacks an explicit verb like 'get' or 'show', but the scope is unambiguous and distinguishes it from general system-status siblings.

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: the content list suggests this tool is for network diagnostics and internet connectivity checks. However, there is no explicit guidance about when to prefer network_status over system_status, system_info, or other related sibling tools.

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