ibmcloud_resource_service_instances

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

With no annotations provided, the description must disclose behavior on its own. It only says 'List', implying a read-only operation, but gives no detail about pagination, scope (e.g., all instances vs. per resource group), or response shape. This is a minimal disclosure for a list tool.

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, direct phrase with no wasted words. It is front-loaded and appropriately sized for a simple list action, though it could add a bit more context without becoming verbose.

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 (optional filters, no required params, no output schema), the description is minimally adequate. It states the core purpose but lacks extra context like filtering behavior or how results are returned, which would improve completeness.

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% (both service_name and resource_group have descriptions), so the schema already explains the parameters. The description adds no additional parameter semantics, but the baseline of 3 is appropriate since the schema carries the load.

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 action (List) and resource (service instances), making its purpose evident. It differentiates from singular sibling tools like 'ibmcloud_resource_service_instance' via the plural form, but doesn't explicitly call out this distinction or contrast with 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?

No information about when to use this tool versus alternatives. Sibling tools include many other list commands (e.g., ibmcloud_cf_apps, ibmcloud_ks_clusters), and the description provides no contextual guidance or exclusions.

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