pentest_osint_takeover

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

No annotations are supplied, so the description carries the full behavioral burden and largely fails it. It does not say whether this performs live DNS resolution (and thus generates external traffic), whether it is read-only, how many CNAMEs/cloud providers it inspects, or whether it silently returns only confirmed takeovers. Only the detection target is disclosed.

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 tight sentence with the detection target front-loaded and zero filler. It is efficient, though the brevity is partly the cause of the missing guidance rather than a virtue of good structuring.

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?

With no annotations, no output schema, and an undocumented second parameter, the description leaves too much unsaid for an agent to invoke this correctly — nothing about inputs, required scope, or what a positive vs. empty result means. For a network-touching security tool, this falls well short of complete.

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% for both parameters. 'domain' is weakly inferable from the wording, but 'candidates' is entirely opaque — the description never says whether it is a list of subdomains to test, pre-resolved CNAME targets, or service fingerprints, nor what happens when it is null/default.

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?

States a specific verb ('check for') and a concrete resource ('dangling CNAMEs pointing at claimable services'), and names the outcome class ('subdomain takeover'). This is clearly distinguishable from DNS/subdomain siblings like pentest_recon_dns or pentest_recon_subdomains, though the description never explicitly contrasts them.

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 when-to-use or when-not-to-use guidance, no prerequisites (e.g., that an engagement/scope must be loaded first), and no named alternative. The agent must infer from the phrase 'subdomain takeover' that this is a narrow, opportunistic check rather than part of routine DNS recon.

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