list_ip_addresses

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It only says 'Get a list of IP addresses,' which simply restates the tool's name and gives no information about side effects, return format, pagination, or required permissions. This is essentially a tautology with no added context.

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, concise sentence with no irrelevant information. However, given the tool's complexity (8 optional parameters), the description is too sparse and lacks structure to guide the agent. It is not appropriately sized for the tool's richness, earning a mid-range score.

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?

The tool has 8 parameters, no annotations, and no output schema, so the description alone must provide a complete picture. It only states what the tool does, omitting any detail about parameter semantics, filtering, or return values. This is inadequate for an agent to use the tool correctly.

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 has 8 parameters with 0% description coverage, and the description provides no information about what any of these parameters (e.g., fqdn, status, address) do or how they affect the list results. Since the description must compensate for the schema gaps, it completely fails to do so, leaving the agent without any understanding of the parameters.

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 clearly states the tool retrieves IP addresses with a specific verb ('Get a list') and resource ('IP addresses'). It distinguishes itself from sibling tools like get_ip_address, which retrieves a single address, and create_ip_address, which creates a new one. However, it does not mention that the list can be filtered by the provided parameters, which could add additional clarity.

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 usage context is provided. The description does not state when to use this tool versus alternatives, such as get_ip_address for a single address or create_ip_address for creating one. There is no mention of filtering capabilities or prerequisites, leaving the agent without guidance on selecting this tool.

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