full_recon

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

No annotations are provided, so the description carries full burden. It mentions that tools run in parallel and returns combined raw results, adding some behavioral context. However, it does not disclose potential side effects, resource intensity, or permission requirements, which are important for a tool that runs multiple scans.

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 three sentences, front-loaded with the main purpose and a clear list of included tools. Every sentence adds value without redundancy. It is appropriately concise for the tool's complexity.

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 simple input schema, lack of annotations, and presence of an output schema, the description is mostly complete. It states the tool runs in parallel and returns combined results, and that the client should generate summaries. However, it could mention that this is a heavy operation or note potential timeouts.

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 has a single 'domain' parameter with no description (coverage 0%). The description mentions 'domain' in context but does not add format, examples, or constraints beyond the schema. The parameter is simple, so the lack of additional semantics is minimally detrimental.

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 it runs all recon tools (WHOIS, DNS, port scan, SSL, tech stack) on a domain in parallel. It specifies the verb 'Run' and the resource 'all recon tools on a domain', distinguishing it from sibling tools that each perform a single scan.

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 implies use this for comprehensive recon and lists the included tools, but does not explicitly state when to use this vs the individual sibling tools or provide alternatives. The context is clear enough for an 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.