pentest_recon_subdomains

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

With no annotations provided, the description carries the full burden, and it does disclose two real behavioral traits: the prefix list is bounded and the operation is rate limited. It does not state whether scope checking is enforced ('scoped domain' is suggestive but vague), what the response contains, or how the rate limit manifests to the caller.

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?

A single compact sentence with the core action front-loaded and the two operational constraints appended parenthetically. Nothing is wasteful, though the brevity comes at the cost of the missing details noted elsewhere.

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?

No output schema, no annotations, and two parameters at 0% description coverage make this thin. For a recon tool whose results feed downstream enumeration, an agent would want to know roughly what is returned and how the optional prefixes argument changes the scan.

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 both parameters are undocumented in the schema and the description must compensate. It does not explain what 'prefixes' does (an optional override list defaulting to null) or what form 'domain' should take, leaving the caller to guess the main behavioral knob of the 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 names a specific verb ('Resolve') and a specific resource ('common subdomain prefixes for a scoped domain'), which is more precise than the generic sibling pentest_recon_dns. It does not explicitly contrast itself with siblings such as pentest_osint_crtsh or pentest_recon_dns, so the differentiation is implied rather than stated.

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?

There is no explicit when-to-use guidance and no named alternative. The parenthetical '(bounded list, rate limited)' hints at a constrained enumeration approach, but an agent gets no instruction on when to pick this over pentest_osint_crtsh or pentest_recon_dns for subdomain discovery.

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