registry_get_network

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

The description only indicates a read operation ('Get'), but with no annotations, it fails to disclose any behavioral traits such as whether the network configuration is persistent, if special permissions are needed, or if any side effects exist. The description lacks detail beyond the basic action.

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 a single, concise sentence with no wasted words, but it is overly terse. Given the complexity of the tool and lack of annotations, it could benefit from additional details without becoming verbose. It is minimally adequate.

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?

With no output schema and minimal description, the tool is incomplete for an AI agent. The return value is unspecified, parameter semantics are missing, and usage context is absent. The description does not suffice for correct 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 input schema has 0% description coverage, and the description does not explain the 'system_hive' parameter, such as expected format (file path, registry key path?) or constraints. The description adds no meaning beyond what the schema provides.

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 it retrieves network configuration from the SYSTEM hive. The verb 'Get' and resource 'network configuration' are specific, and the source is identified. It distinguishes itself from sibling registry tools like registry_get_key or registry_get_system_info, though it could be more explicit about what network configuration entails.

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 versus alternatives, such as registry_get_system_info for broader system information or registry_search for arbitrary queries. There is no mention of prerequisites or context where this tool is appropriate.

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