cloud_list_primary_ips

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

Description adds 'Read only, free, compact by default', providing useful behavioral context beyond the name. However, no annotations exist, and details like pagination, rate limits, or what 'compact' means are missing, leaving gaps.

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 concise: three short sentences with no filler. Every sentence contributes value, stating purpose, safety, and default behavior.

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 listing tool with 3 optional parameters and no output schema, the description covers core aspects but lacks details on output format, filtering via query parameter, and any limits. Adequate but not fully complete.

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 coverage is 100%, so baseline is 3. The description's mention of 'Compact by default' explains the default behavior of the 'verbose' parameter, adding value beyond the schema. Other parameters are well-described in schema.

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?

Clearly states 'List primary IPs', specifying both the action and resource. However, it does not explicitly differentiate from sibling tools like cloud_list_floating_ips, which also lists IPs on the Cloud platform.

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 on when to use this tool versus alternatives. Merely states 'Read only, free', which implies safety but does not provide context for decision-making or exclusions.

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