ibmcloud_config_list

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. The verb 'List' implies a read-only operation, but the description does not specify what is returned, whether authentication is required, or any side effects. It adds minimal context beyond the tool name.

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 a single short sentence, 'List CLI configuration', with zero fluff. It is front-loaded, immediately conveying the action and resource. It is appropriately sized for such a simple tool, though it could be seen as under-specification, it is perfectly concise.

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 the tool's low complexity (zero parameters, no output schema, no annotations), the description is minimally viable. It tells the agent the operation but is vague about the exact content of the output or any prerequisites. For a simple list tool, this might be acceptable, but it leaves a gap in setting 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?

The tool has zero parameters, and the schema is an empty object with 100% coverage. Per the baseline guidance for 0 params, this is a score of 4. The description does not need to add parameter details since there are none.

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 'List CLI configuration' clearly states the action (list) and resource (CLI configuration), which is specific enough to differentiate from sibling tools like ibmcloud_cf_apps or ibmcloud_resource_groups. However, it lacks detail on what exactly constitutes 'CLI configuration' (e.g., target, account, API endpoint), which could be ambiguous.

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 guidance on when to use this tool versus alternatives. The description merely states what it does without mentioning prerequisites (e.g., requiring login) or situations where it's appropriate. No exclusions or alternative tools are referenced.

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