aws_call

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

With no annotations, the description carries the full behavioral burden and does so well: reads auto-paginate and run read-only; mutation requires mutate=true plus dangerous guard mode; destructive verbs are refused unless enabled in config and even then require a two-phase token confirm where the first call does not touch AWS; region/account pin the call. This is exactly the safety, reversibility, and execution-flow detail an agent needs.

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?

Front-loaded with the core purpose and boundary before the safety rules, and nearly every clause earns its place (pagination, mutation gating, two-phase confirm, pinning). It is a dense single block that would read better split into bullets, but it is not padded.

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 an 8-parameter, nested, no-output-schema generic passthrough, the description covers the operational essentials: scope, pagination, mutation/destructive safety, and region/account pinning. It does not describe the shape of the returned boto3 response, which is a minor gap for a generic passthrough.

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%, so the schema already documents all 8 parameters and the baseline is 3. The description reinforces the operation naming convention and params PascalCase format, and adds a little on region/account pinning, but does not mention max_items and adds little beyond the schema.

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?

States a specific mechanism (boto3 passthrough), a clear scope (the AWS read surface), and enumerates the operation patterns it covers (Describe*/Get*/List*/Filter*/Lookup*) with concrete examples. It draws an explicit boundary against pre-wrapped siblings ('that isn't pre-wrapped'), so an agent can tell it apart from aws_list_regions, s3_list_buckets, etc. without opening any schema.

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?

Explains when to reach for it (operations not already pre-wrapped, with example method names) and when mutating/destructive paths apply (mutate=true, dangerous guard mode, two-phase confirm). It implies the pre-wrapped siblings should be preferred for common ops but does not name a specific sibling to route to, so it falls short of explicit when-not guidance.

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