enumerate

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

No annotations are provided, so the description must fully disclose behavioral traits. While the description mentions many techniques, it does not state whether the tool is destructive, requires authentication, has rate limits, or provides any output format details. This is a significant gap for a tool performing multiple phases of operations.

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 front-loaded with 'Scope expansion' but then lists 8 techniques in a verbose manner. While informative, it could be more concise. The summary '8 techniques across 3 phases' adds structure but the description overall feels slightly bloated for a parameter of one.

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 complex nature of the tool (8 techniques, 3 phases) and lack of output schema, the description provides a high-level overview of capabilities but omits details on phases, output format, or expected behavior. It partially compensates for missing annotations but is not fully complete for an agent to understand all aspects.

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 schema has 100% coverage for the single 'domain' parameter with description 'Target domain for scope expansion'. The tool description adds additional meaning by listing the specific enumeration techniques applied, providing context that helps the agent understand the scope of operations, going beyond the simple schema description.

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 the tool's purpose: scope expansion through various enumeration techniques like subdomain enumeration, wildcard DNS detection, TLD expansion, etc. It uses specific verbs and clearly distinguishes from sibling tools such as scan_dns or analyze, which focus on scanning or analysis.

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 does not explicitly state when to use this tool versus alternatives. While the context of 'scope expansion' implies it is for initial reconnaissance, there is no guidance on prerequisites or when not to use it, leaving the agent to infer usage.

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