sdcloud_list_icap_servers

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

No annotations provided, so the description must disclose behaviors. It mentions optional features but lacks details on default sorting, result limits, or performance implications. As a read-only operation, it is safe, but more context would be beneficial.

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?

Single sentence, clear, and front-loaded with the core action and resource. Efficient but could be structured with bullet points for optional features.

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 no output schema, the description does not explain return format or limitations. It is sufficient for basic invocation but lacks completeness for agents needing detailed behavioral expectations.

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 all parameters are described in the schema. The description reinforces that pagination, filtering, and sorting are optional but does not add meaning beyond what the schema provides, such as filter syntax.

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 the verb 'List', the resource 'ICAP server objects', and highlights optional pagination, filtering, and sorting. It effectively distinguishes from siblings like 'sdcloud_list_icap_profiles' and other list tools.

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?

The description indicates that pagination, filtering, and sorting are optional, but does not explicitly guide when to use this tool over alternatives like 'sdcloud_get_icap_server' or other list tools. No 'when not to use' or alternative mentions.

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