amass

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

No annotations are provided, so the description carries full burden. It only states 'Advanced subdomain enumeration' with no details on how it behaves—e.g., scanning depth, concurrency, output format, or potential risks. This is insufficient for an agent to predict side effects.

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 (three words), but it sacrifices informativeness for brevity. It is under-specified and does not justify its conciseness by being complete. A single sentence could have been more helpful.

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 of subdomain enumeration tools (sibling: subfinder, dnsrecon) and the absence of output schema, annotations, or parameter descriptions, this description is woefully incomplete. An agent would lack critical operational details needed to invoke the tool correctly.

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 0% and the description adds no meaning to the parameters. The 'session_id' parameter is unclear without context, and 'domain' is obvious from the tool name. The description fails to compensate for the lack of schema documentation.

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 states it performs subdomain enumeration, which is a specific verb and resource. However, it does not differentiate from the sibling tool 'subfinder' which also performs subdomain enumeration. The word 'advanced' hints at more capability but lacks explicit distinction.

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?

No guidance is provided on when to use this tool over alternatives like subfinder or other enumeration tools. There is no mention of prerequisites, contexts, or exclusions, leaving the agent without decision-making support.

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