ip_pools

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

With no annotations, the description carries the behavioral burden; it does disclose the key trait 'Read-only,' which correctly signals a safe, non-mutating operation. It adds nothing further — no permission requirements, scope, or pagination behavior — so it is adequate but thin for the full burden it must bear.

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?

Extremely compact and front-loaded: verb+resource first, returned fields second, safety trait last. Every fragment carries information, though the endpoint path is marginal.

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?

An output schema exists, so return-value explanation is unnecessary, and 'Read-only' covers the safety profile. However, the undocumented required parameter and lack of any scope or when-to-use context leave the definition minimally complete for a device-scoped list 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?

The single required parameter device_name has 0% schema description coverage, and the description never mentions it. The agent gets no indication of what device_name identifies or its expected format, leaving the one parameter the tool requires entirely undocumented.

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 (List), resource (IP pools), the backing endpoint (/ip/pool), and the returned fields (name, ranges). An agent can distinguish it from siblings like ip_addresses or ip_routes by resource name, though the description never explicitly contrasts them.

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?

Aside from 'Read-only,' there is no when-to-use guidance, no prerequisites, and no mention of alternatives among the many ip_* siblings. The agent must infer the use case from the resource name alone.

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