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

No annotations are provided, so the description bears the full responsibility for disclosing behavior. It only states the action and lists tool options, but does not mention output format, potential side effects, authentication requirements, or any operational constraints. This is a significant gap for a tool that likely performs network scanning.

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 concise and front-loaded with the purpose, but it is under-specified. While it is not verbose, it sacrifices essential information for brevity. The two sentences are easy to parse, but they omit critical context that an agent needs to invoke the tool correctly.

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 tool has three required parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain what 'recon' entails, what the return value looks like, how the api_key is used, or any error handling. An agent would struggle to know what to expect or how to provide valid inputs.

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%, so the description must explain all parameters. It only elaborates on the 'tool' parameter by listing valid values (nmap, subfinder, etc.). The 'target' and 'api_key' parameters are left unexplained, and the description does not clarify their formats or purposes. This is insufficient for a 3-parameter tool.

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: 'Run recon against an external target' and enumerates the supported sub-tools in the tool parameter. This distinguishes it from the sibling tools, none of which are recon-related, so an agent can easily identify when this tool is relevant.

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?

Usage is implied rather than explicit. The description implies that this tool is for recon, but it does not state when to use it over alternatives, nor does it mention any prerequisites or exclusions. Since the sibling tools are unrelated, the context is somewhat clear, but there is no direct guidance.

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