run_cloudfox

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

With no annotations provided, the description must fully convey behavioral traits. It fails to mention whether the tool modifies the environment, requires AWS credentials, or has side effects. The single sentence offers no insight into the tool's impact or requirements.

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 a single, clear sentence with no superfluous words. It is as concise as possible while conveying the core purpose.

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 simplicity of the tool (2 optional parameters, no output schema), the description is incomplete. It lacks context about the tool's typical output, whether it is safe to run in read-only mode, and what 'enumerate the attack surface' entails in practice.

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?

Both parameters have descriptions in the input schema (profile and command_type), giving 100% coverage. The tool description adds no additional meaning beyond what the schema already provides, such as acceptable values for command_type or how the profile parameter is used.

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 'Enumerate the attack surface of an AWS environment' clearly states the tool's purpose: to run CloudFox for AWS enumeration. It distinguishes run_cloudfox from sibling tools that target different domains (e.g., network scanning with run_nmap, web enumeration with run_ffuf).

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 provides no guidance on when to use this tool versus alternatives like run_nuclei or run_searchsploit. There is no mention of prerequisites, common use cases, or scenarios where this tool is inappropriate.

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