Get security group capabilities

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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, and the description goes further by disclosing the exact permission model (networking:read vs networking:manage), that read/full defaults do not grant networking, and that the backend enforces ownership, feature availability and 2FA locks. That is substantive governance context beyond what structured fields provide.

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 tight sentences with the core capability statement front-loaded, followed by the permission/authorization constraints. No filler, though the second sentence is dense with policy detail.

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 parameters, no output schema, and rich annotations, the description covers the important behavior: what is read and the permission/enforcement context. It stops short of describing the shape of the returned capability data, but little more is required for a zero-arg read.

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 per the baseline a 4 applies. The description adds no parameter guidance, but none is needed since the schema is empty.

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 ('Read') and resource ('security-group availability'), plus the concrete capability queried ('whether the network default policy can be changed'). It does not differentiate itself from close siblings like get_networking_capabilities or get_network_appliance_capabilities, which use the same 'capabilities' framing, so an agent must infer the distinction.

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?

Provides an important precondition (requires explicit networking:read; defaults do not grant networking), which is real usage context. However, it never states when to pick this tool over the similarly named networking capability siblings, leaving the choice largely implicit.

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