umbrella_list_internal_networks

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

With no annotations provided, the description carries the behavioral burden. 'List' clearly implies a read-only operation, and the target scope is stated. It does not disclose pagination behavior, authorization needs, or result format, but for a non-mutating list tool this is adequate though not rich.

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 filler or redundancy. It front-loads the action and resource, and every word contributes meaningful scoping.

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 list tool, the description plus the fully documented parameter schema is mostly sufficient, and no output schema means return values need not be described. The main gap is the missing explicit differentiation from sibling list tools, particularly umbrella_list_networks.

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 covers all three parameters (limit, offset, additionalParams) with descriptions, so the 100% coverage baseline applies. The tool description adds no parameter-specific meaning beyond what the schema already 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 uses a specific verb ('List') and identifies the resource: internal (RFC1918) networks registered for internal-network identities. The parenthetical 'RFC1918' adds precision and helps separate this from a generic network-list tool. It does not explicitly reference sibling umbrella_list_networks, so full differentiation is left partly to the tool name.

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 scoping qualifiers 'internal (RFC1918)' and 'registered for internal-network identities' imply when this tool is appropriate. However, the description does not explicitly mention alternatives such as umbrella_list_networks or state conditions for choosing one over the other.

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