sdcloud_list_icap_profiles

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

No annotations are provided, so the description carries full burden. It mentions pagination, filtering, and sorting but does not disclose if the operation is read-only, requires specific permissions, or has any side effects. The lack of behavioral detail is a significant gap.

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 very concise (10 words), but it is so brief that it fails to provide enough context for an AI agent. Conciseness is good, but it comes at the cost of completeness.

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?

There is no output schema and the description does not hint at what the response contains (e.g., list of profile IDs, full objects). For a list tool with 5 optional parameters, the description is incomplete.

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%, with each parameter documented in the input schema. The description's mention of 'optional pagination, filtering, and sorting' is a high-level summary that adds marginal value beyond the 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?

The description clearly states it lists ICAP profile objects, with optional pagination, filtering, and sorting. The verb 'list' and resource 'ICAP profile objects' are specific, but it does not differentiate itself from sibling list tools like sdcloud_list_ipsec_profiles aside from the resource type.

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 is provided on when to use this tool versus alternatives like sdcloud_get_icap_profile (for a single profile) or sdcloud_create_icap_profile. The description does not explain when pagination or filtering is beneficial.

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