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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered by structured fields. The description adds no further behavioral context such as error handling for unknown IDs or what the returned network contains, so it earns only the baseline credit.

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 first sentence is tight and front-loaded, but the second sentence explains 'criticality', which is not a parameter of this tool and reads like content carried over from create/update_infrastructure_network. That sentence costs space without helping an agent call this tool.

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 one-parameter read tool with no output schema this is minimally adequate: it confirms the lookup is by ID. It says nothing about the shape of the returned network or failure behavior, and the stray 'criticality' note is unexplained.

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% with a single documented 'id' parameter, so the schema already carries the semantics and a 3 is the baseline. The description adds no format detail for the ID, and its mention of 'criticality' refers to something outside the input schema, adding confusion rather than meaning.

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 specific verb ('Get') and resource ('a single infrastructure network by ID'), which cleanly separates it from the sibling list_infrastructure_networks and the create/update/delete network tools. An agent can identify the operation without opening the schema.

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 'single ... by ID' phrasing implies you need a known network ID and should use list_infrastructure_networks to discover one, but no when-to-use or when-not-to-use guidance is stated. Usage is inferable rather than explicit.

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