list_connectionsList the cloud accounts this API key can scan, with their status.
Only a connection with status CONNECTED or VERIFIED can be scanned. PENDING means the human hasn't created the CloudFormation stack yet.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, so safety is covered. The description adds meaningful behavioral context by clarifying the meaning of statuses, especially PENDING with the CloudFormation stack reference, which enriches the agent's understanding of the output.
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 exceptionally concise: two sentences, front-loaded with the main purpose, and each additional sentence adds important interpretation for statuses. No fluff or repetition.
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?
For a simple no-parameter, read-only list tool, the description effectively covers the scope (what the API key can scan) and the meaning of statuses. It does not detail the output structure, but given the simplicity and lack of an output schema, this is acceptable and nearly complete.
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 baseline for zero parameters is 4. The description adds no parameter documentation (there is nothing to document), so the baseline applies.
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 uses a specific verb 'List' and identifies the exact resource ('cloud accounts this API key can scan') with their status. It clearly distinguishes from siblings like get_connection (singular) and create_cloud_connection (creation).
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?
Provides clear context by explaining that only CONNECTED or VERIFIED statuses are scannable and what PENDING means. It does not explicitly contrast with alternate tools (e.g., get_connection) or state when to use this over others, but the context is clear and useful for the agent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct resource and action: connection lifecycle (create, verify, get, list), job lifecycle (run, get status, get result), and findings (list). Even get_job_result and list_cost_findings are clearly differentiated as raw vs. analyzed data, and whoami/list_tools_available serve metadata purposes.
Most tools follow a consistent verb_noun pattern (create_, get_, list_, run_, verify_). The only outlier is 'whoami', which breaks the pattern but is a recognizable convention for account identification. Overall naming is predictable and readable.
With 10 tools, the set is well-scoped for a cloud cost scanning platform. Each tool serves a clear purpose in the connection-scan-result workflow, with no redundancy or bloat.
The core scan workflow is covered (connect, verify, scan, get job, get findings), but there are notable gaps: no tool to delete/disconnect a cloud account, and no way to list past jobs or retrieve results without a prior job_id. These missing lifecycle/history operations could force agents to rely on external state or fail when context is lost.