List networking operations

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

Goes well beyond the readOnly/idempotent annotations by disclosing the exact auth scopes required ('networking:read' vs 'networking:manage'), that full/read defaults do NOT grant networking, the absence of pagination, and that the backend enforces ownership, feature availability and 2FA locks. This is rich, actionable behavioral context.

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?

Two sentences with the core read action front-loaded, followed by the auth/environment constraints. Dense but every clause (no pagination, scope requirements) carries real weight; only the semicolon-chained auth sentence is a touch heavy.

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 parameterless, no-output-schema listing tool, the description covers the key unknowns: auth scope requirements, lack of pagination, the has_more signal, and backend enforcement. It lacks any hint of what an 'operation' record contains, but annotations and low complexity keep that a minor gap.

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; the baseline for a no-param tool is 4. The mention of operations_has_more refers to the response, not an input, so it neither helps nor hurts parameter understanding.

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?

States a clear verb+resource ('Read recent network operations') and even names the response field operations_has_more. It does not explicitly differentiate from the sibling get_networking_operation (singular), but the list scope is unambiguous.

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?

Implies usage as a recent-operations listing and adds the important note that 'this endpoint has no pagination parameter', but it never says when to use this versus get_networking_operation or get_network_appliance_operation. Usage is left to inference.

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