bb_takeover

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

No annotations are provided, so the description must fully disclose behavior. It mentions methods but does not clarify if the tool is read-only (non-destructive) or if it performs any actual takeover actions. It also omits any mention of authentication needs, rate limits, or potential side effects.

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 very concise, stating the purpose and methods in a single line. However, it lacks structure and does not include parameter explanations or usage notes, which reduces its helpfulness despite its brevity.

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 4 parameters, no annotations, and an output schema (unseen), the description is severely incomplete. It does not cover return values, behavior specifics, or how to effectively use the tool, leaving significant gaps for an AI agent.

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 4 parameters (domain, proxy, timeout, auth_token) with 0% documentation coverage. The description does not explain any of these parameters, leaving the agent to guess their meaning and usage.

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: subdomain takeover detection. It specifies the methods used (DNS CNAME analysis, cloud service pattern matching for 50+ services, HTTP verification), which distinguishes it from sibling tools like bb_subdomain (likely just enumeration) and other vulnerability scanners.

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?

No explicit guidance on when to use this tool versus alternatives like bb_subdomain. The context implies it's for after subdomain enumeration, but there is no mention of prerequisites, when not to use, or how it fits into a workflow.

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