aws_call

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

The description reveals that parameters are passed exactly as AWS documents them, indicating a passthrough to the AWS API. However, with no annotations provided, it fails to disclose potential side effects (e.g., mutating resources), authentication requirements, or what happens on errors or returns, leaving the agent without a full picture of the tool's behavior.

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 three sentences, front-loading the core purpose and then explaining each parameter in a clear, linear structure. While it could be slightly more compact, it is efficient and well-organized, with no unnecessary filler.

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 tool's generic nature (any AWS API call) and the absence of an output schema, the description does not explain what the tool returns after execution, how to interpret errors, or any prerequisites like authentication. These gaps leave the agent under-informed for a potentially complex operation.

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?

Each parameter is explained in detail: service includes boto3 service name examples (ec2, s3, lambda, rds); action provides both PascalCase and snake_case examples (RunInstances vs run_instances); params is defined as a JSON object exactly as AWS documents, with a bucket example. This substantially adds meaning beyond the schema's bare types and required flags, fully compensating for the 0% schema description coverage.

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 that the tool calls any AWS API operation against a local Floci instance, specifying the verb 'Call' and the resource 'any AWS API operation' on the target. It distinguishes itself from sibling tools by being generic, though it doesn't explicitly compare, the purpose is unambiguous and specific.

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?

There is no guidance on when to use this tool versus the sibling tools (floci_status, floci_inventory). The description does not mention alternatives, exclusions, or prior conditions, leaving the agent to infer that it's for arbitrary AWS calls without knowing when the siblings would be more appropriate.

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