amass

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It merely states 'Advanced subdomain enumeration' with no mention of side effects, permissions, rate limits, or output format. This is a severe gap for a scanning tool. Score 1 for minimal and insufficient transparency.

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 concise (3 words) but at the cost of informativeness. It lacks any structure or detail. Conciseness without substance is under-specification. Score 2 for minimal length but poor information density.

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 and the rich set of sibling tools, the description is woefully incomplete. No output schema, no annotations, and cryptic parameter names (session_id, dry_run) exacerbate the lack of context. Score 1 for failing to provide adequate completeness.

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 low (33%), only describing dry_run. The description adds no parameter meaning beyond the schema. For a 3-parameter tool, this is inadequate. Score 1 for failing to compensate for low schema 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 'Advanced subdomain enumeration' clearly identifies the tool's purpose: enumerating subdomains. The verb 'enumerates' is implied. However, it does not distinguish itself from sibling tools like subfinder or dnsrecon, making it somewhat generic. Score 4 for clear verb+resource but lacking differentiation.

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. Among 30 sibling tools, many (e.g., subfinder, dnsrecon) also enumerate subdomains. There is no information on prerequisites, context, or exclusions. Score 2 for absence of usage guidance.

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