snapshot_aws

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

No annotations are provided, so the description carries full burden. It mentions 'live-scan' implying real-time data retrieval, but does not disclose potential side effects, permissions, rate limits, or whether it modifies state. Annotations would have helped, but the description adds some context beyond the schema.

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 concise, with a clear one-sentence summary followed by parameter explanations in a standard docstring format. No unnecessary words, but could be slightly more structured (e.g., bullet points).

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 complexity (3 parameters, no annotations, but has output schema), the description adequately explains the tool's purpose and parameters. It references a sibling tool (list_aws_accounts) for account_id, which helps. The output schema exists, so return values need not be described.

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 coverage is 0% (no descriptions in schema), so the description must compensate. It explains each parameter: account_id (from list_aws_accounts), region (with example), and service (with examples). This adds significant meaning beyond the schema's bare property names.

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 it takes a 'live-scan snapshot' of an AWS service via Cloudcraft, specifying the exact action (snapshot) and resource (AWS service). This distinguishes it from sibling tools like create_blueprint or export_blueprint_image.

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 implicitly indicates this is for scanning live AWS services, and the mention of list_aws_accounts for getting account_id provides cross-reference. However, it does not explicitly state when not to use it or mention alternatives.

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