ovh_get_ips

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

No annotations are present, and the description provides no behavioral information. It does not disclose whether the tool is read-only, requires specific authorization, or has any side effects. The agent gains no insight into what happens when this tool is called beyond the bare action.

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 concise at three words, but it is under-specified. While brevity is valued, the lack of additional context or structure means the description does not fully earn its place; it could be expanded to clarify purpose.

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?

Given the tool has no parameters, no output schema, and no annotations, the description fails to provide sufficient context. It does not explain what 'IP addresses' refers to (e.g., public IPs, private IPs, for which services), leaving the agent uncertain about the tool's scope and usefulness.

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 input schema has no parameters, so the description does not need to add parameter meaning. The baseline for zero parameters is 4, and there is no missing information regarding 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 states the verb 'Get' and resource 'IP addresses', which is minimally clear but vague. It does not specify the scope (e.g., all IPs associated with the account, or for a particular service), nor does it distinguish from sibling tools that might also involve IPs, such as ovh_get_vps.

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 guidelines are provided. The description does not indicate when to use this tool versus alternatives, nor does it mention any prerequisites or context for invocation.

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