iaas_get_network_profiles

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety is covered without the description. The description adds only the raw GET path — no pagination defaults, no response shape, no note on whether the full collection is returned or paged by `top`/`skip`.

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?

Three lines say the same thing twice ("Get network profiles" / "Get all network profiles") plus a raw endpoint. The repetition consumes the limited space without front-loading any additional value.

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 six-parameter paginated list endpoint with no output schema, an agent still needs to know what is returned, whether results are paged by default, and how this differs from the single-profile fetch. None of that is present.

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 description coverage is 100% across all six parameters (top, skip, count, filter, select, apiVersion), so the schema carries parameter meaning. The description adds nothing beyond that, which lands at the baseline of 3.

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 names a clear verb and resource ("Get all network profiles") and even the underlying endpoint, so the basic operation is unambiguous. However, it never distinguishes this collection read from the singular sibling `iaas_get_network_profile`, and the same fact is repeated three times rather than adding scope detail.

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?

There is no statement of when to use this tool versus `iaas_get_network_profile`, `iaas_create_network_profile`, or `iaas_update_network_profile`, despite obvious siblings in the tool list. Usage is only implied by the name.

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