Get networking overview

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds genuinely non-obvious context beyond that: the explicit networking:read/networking:manage scope requirement, the fact that full/read defaults do not grant networking, and backend enforcement of ownership, feature availability and 2FA locks.

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?

Three sentences, front-loaded with the purpose before the auth and enforcement caveats. Each sentence carries distinct information, though the auth/enforcement clauses are dense and could be trimmed slightly.

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, the description must convey return content, and it does identify networks, quota and an operation snapshot plus the operations_has_more signal. It stops short of enumerating the snapshot's fields, but it is sufficient for a zero-parameter read tool.

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 tool takes zero parameters, so there is nothing for the description to document; baseline 4 applies. The mention of operations_has_more is a response-field note rather than a parameter, and it is not misleading here.

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 names a specific verb (Read) and concrete resources (owned networks, quota, operation snapshot), which is more than a tautology of the title. However, it never distinguishes itself from close siblings such as get_networking_topology, get_networking_capabilities, or get_networking_features, leaving the agent to guess which overview to call.

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?

It supplies a real precondition ('Requires explicit networking:read for reads or networking:manage for changes; full/read defaults do not grant networking'), which helps the agent decide whether it is even permitted to call this. It does not, however, state when to prefer this tool over the other networking read tools, so usage is only implied.

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