list_ip_prefix_delegations

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a read-only operation through the word 'List', but gives no information about pagination, result shape, empty-result behavior, or any side effects. It adds no behavioral context beyond what the tool name already communicates.

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 a single six-word sentence with no filler and a clear, direct structure. It is appropriately front-loaded, though its brevity means it sacrifices behavioral and contextual 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?

For a simple list operation with two required parameters and full schema coverage, this is minimally viable: an agent can infer what to call and which IDs are needed. However, with no annotations or output schema, the description leaves gaps around what a delegation is, how results are returned, and how this operation fits with the broader IP prefix workflow.

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 schema describes 100% of parameters with clear descriptions for 'prefix_id' and 'account_id', so the high-coverage baseline applies. The tool description adds no parameter-level meaning, such as value formats or the relationship between the two IDs.

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 clear verb ('List'), resource ('delegations'), and scope ('for an IP prefix'), which matches the tool name and distinguishes it from related prefixes tools like list_ip_prefixes or get_ip_prefix. However, it adds little beyond the tool name and does not explicitly contrast with any sibling tool.

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?

No guidance is provided on when to use this tool versus other prefix-related tools. The description only restates the action and does not mention prerequisites, exclusions, or how this differs from get_ip_prefix_bgp_status or list_addressing_services.

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