iaas_get_external_ip_blocks

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful domain context by explaining that external IP blocks come from an external IPAM provider and can be used to create subnetworks, but it does not disclose return format, pagination behavior, or other behavioral traits beyond annotations.

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 description is short and front-loads the operation with "Get all external IP blocks" before adding a definition and endpoint. It is mostly efficient, though the endpoint line duplicates information already present in the annotation 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?

For a simple read-only list tool with one optional parameter and no output schema, the description is nearly sufficient: it states the operation and defines the resource. The main missing context is whether results are paginated or how they relate to the singular iaas_get_external_ip_block sibling, but annotations already carry the safety profile.

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%, and the single optional apiVersion parameter is fully documented in the schema. The description does not add any parameter-level meaning, so the baseline score of 3 is appropriate.

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: "Get all external IP blocks." It clearly identifies the operation as listing external IP blocks, but it does not distinguish this plural-list tool from the sibling singular tool iaas_get_external_ip_block or other IP-range tools.

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 provides domain context by defining an external IP block, but it gives no explicit guidance on when to use this tool versus alternatives. It does not mention the singular sibling tool, pagination expectations, or any exclusion conditions.

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