Get network appliance operation

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

Annotations already declare the safe read-only, idempotent profile, yet the description adds substantial context beyond them: poll cadence, the meaning of waiting reason_kind, the rule that creation only succeeds when resource state and health confirm readiness, and the permission model (networking:read vs networking:manage, defaults insufficient). It also notes 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?

The purpose is front-loaded in the first clause and every sentence carries operational information about states, timing, or permissions. It is dense and semi-colon-heavy, but there is no filler or repetition of the title.

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 carry the return-value burden, and it does: it names the status progression and the terminal states an agent should test against. It stops short of describing the full response shape or which fields confirm readiness, leaving a small gap for a polling 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 single operation_id parameter is fully documented in the schema (UUID pattern, length bounds, ownership note), giving 100% coverage, so the baseline is 3. The description adds only an implicit 'owned' qualifier and no additional syntax or sourcing detail beyond the schema.

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 states a specific verb and resource: polling an accepted appliance operation, with the terminal states spelled out (succeeded, failed, cancelled). It is clearly a status-read tool rather than a mutator. However, it never distinguishes itself from the close sibling get_networking_operation, leaving the agent to infer the scope difference from the name alone.

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 gives concrete usage context: poll while on in_progress, wait next_check_seconds between reads, and treat queued/waiting_dependency as progress rather than failure. What is missing is an explicit statement of when to choose this over get_networking_operation or list_networking_operations, so alternatives remain unaddressed.

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