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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds domain semantics about how criticality affects Level of Service enforcement, which is genuine extra context, but it offers nothing about errors when an ID is unknown or about what the response contains.

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 definition is short and the core purpose is front-loaded, which is good. However, the second sentence spends half the description on a `criticality` concept that is not an input parameter, which reads as misplaced or stale text rather than earning its place.

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 single-record read with one fully described parameter and no output schema, the description is nearly sufficient — the agent knows the input and the safety characteristics. The dangling reference to a non-existent `criticality` parameter is the only notable gap in an otherwise complete definition.

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?

Schema coverage is 100% for the single required `id` field, so the baseline is 3. The description adds no format or lookup detail for `id`, and the second sentence discusses `criticality`, which does not appear anywhere in the input schema, so it contributes no actionable parameter guidance.

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 first sentence gives a specific verb+resource+scope ("Get a single infrastructure network by ID"), which cleanly separates it from the sibling list_infrastructure_networks. It doesn't explicitly name that sibling, but the singular/ID framing makes the retrieval-by-key purpose 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?

There is no statement of when to use this tool versus the many get_* siblings or when to reach for list_infrastructure_networks first to find an ID. The description only asserts what the call does, leaving selection entirely to inference from the name.

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