list_aws_accounts

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and reach profile is covered. The description only adds the domain detail that these are Cloudcraft-registered accounts used for live scans; it says nothing about pagination, result ordering, or what happens when no accounts are registered.

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?

A single, front-loaded sentence with no filler. The verb and resource lead, and the qualifier adds scope without padding.

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 zero-parameter read-only list tool with a full output schema, the description covers what an agent needs to select and call it correctly. Return-value details are appropriately delegated to the output schema; only cross-tool routing against list_azure_accounts/snapshot_aws is missing.

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 takes zero parameters, so the baseline of 4 applies. There is no parameter whose meaning the description could clarify or obscure.

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 states a specific verb and resource ('List AWS accounts') and adds useful scope ('registered with Cloudcraft for live-scan snapshots'). It is clearly distinguishable from the sibling list_azure_accounts by naming AWS, though it never explicitly contrasts with it or with snapshot_aws.

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 phrase 'for live-scan snapshots' implies the purpose of listing accounts (discovering targets for snapshot_aws), but there is no explicit statement of when to call this rather than another discovery or snapshot tool. Usage is inferred rather than stated.

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