db_list_deployments

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

No annotations provided, so description must fully communicate behavior. It mentions 'via resource controller' but does not disclose important details like whether the list is paginated, scope (all regions?), or any side effects. Minimal transparency.

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?

Description is a single, front-loaded sentence with no extraneous words. Every word earns its place.

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 parameters and no output schema, the description is minimal but covers the basic purpose. However, it lacks details like typical return structure, permissions needed, or limitations, leaving some gaps for a complete context.

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?

Input schema has no parameters, so schema coverage is 100%. The description adds no parameter meaning beyond that, which is acceptable for a parameterless tool, earning a baseline score 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 clearly states 'List all IBM Cloud database deployments', using a specific verb 'List' and resource 'deployments'. It distinguishes from sibling tools like db_get_deployment (single) and db_create_deployment (create).

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 implies usage when needing an overview of deployments, but lacks explicit guidance on when to use this vs alternatives, such as db_get_deployment for a specific deployment or db_list_backups for backups.

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