cloud_list_networks

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

No annotations exist, so description must fully convey behavior. It only says 'List private networks' without mentioning pagination (implied by page/per_page params), filtering, ordering, or any limitations. The agent lacks critical runtime 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?

Extremely concise (one sentence) and front-loaded. However, it sacrifices necessary detail for brevity, which is acceptable for a simple tool but still leaves gaps.

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 list tool with pagination and optional filtering, the description is incomplete. It does not cover how to use the parameters or what the output contains (though output schema exists). The agent would need additional sources.

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?

With 0% schema description coverage, the description should explain parameter usage, but it does not mention any of the four parameters (page, per_page, name, label_selector). The agent must infer from parameter names alone.

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?

Description clearly states the action (list) and resource (private networks), distinguishing it from create/delete/get single network siblings. However, it could be more explicit about the scope (e.g., 'all' or 'filtered').

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 like cloud_get_network or cloud_create_network. No prerequisites or context provided.

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