tools_amass

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

No annotations are provided, so the description must disclose behavioral traits. 'Execute amass.' reveals nothing about what the tool does, potential network impact, required permissions, or output format. The agent has no idea what side effects or results to expect.

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 extremely short, but this is under-specification rather than concise efficiency. It omits essential information that should be present, making the text of no added value beyond the tool name.

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 lack of annotations, no output schema, and ambiguous parameters, the description is completely inadequate. It does not explain what amass does, when to invoke it, or what it returns, leaving a dangerous gap for a network reconnaissance tool.

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 input schema lists 'domain' and 'additional_args' with zero description coverage. The description 'Execute amass.' does not explain that 'domain' is the target domain or how 'additional_args' should be formatted, leaving the agent to guess parameter usage.

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 'Execute amass.' merely restates the tool name without indicating what amass does (e.g., subdomain enumeration, attack surface discovery). It fails to distinguish the tool from siblings like tools_subfinder or tools_assetfinder, which perform overlapping functions.

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 alternatives. The description provides no context that amass is for passive/active DNS enumeration or how it differs from other reconnaissance tools, leaving the agent without direction for tool selection.

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