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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the mutation and idempotency profile is covered. The description adds one genuinely useful behavioral fact beyond annotations — the required infrastructure_networks:write scope — but says nothing about partial-update semantics or what the destructive hint actually entails.

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 short sentences, zero padding, with the action and target front-loaded before the scope requirement. Every clause earns 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?

With 7 params, a nested metadata object, no output schema and full schema coverage, the description is minimally sufficient: it names the target and the auth requirement. It omits whether unspecified fields are preserved or cleared on update, which matters for a destructive PATCH-style 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?

Schema description coverage is 100%, including the non-obvious null-clearing semantics for criticality, so the schema carries parameter meaning entirely. The description only restates that id identifies the target, adding no syntax or format 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?

States a specific verb and resource ('Update an existing infrastructure network') and pins the identifier ('by ID'), so an agent knows it operates on one existing network rather than creating one. It does not distinguish itself from the many sibling update_* tools, but the resource name is unique enough to disambiguate.

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 description gives no when-to-use or when-not guidance, and no alternatives (e.g., update_infrastructure_zone, create_infrastructure_network) are mentioned. The only conditional it supplies is a scope string, which is a prerequisite rather than usage direction.

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