Takeover Confirm

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

Clearly discloses side effects: fetches the proof URL, checks the target host, and promotes the finding to confirmed. Matches annotations readOnlyHint=false and destructiveHint=true by indicating a state-changing action.

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?

Concise and front-loaded with the exploit/approval flag, followed by a clear action and condition. No unnecessary detail.

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?

Covers the precondition (human approval), the action, and the conditional side effect. Does not describe return values, but that is not critical for tool selection.

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?

Description clarifies proof_url and target host in prose, but the notes parameter is not explained and there are no formal parameter descriptions in the schema.

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 the specific action: verify a live takeover PoC and promote the finding to confirmed. Clearly distinguishes from sibling tools by noting this is the single place a takeover can become 'confirmed'.

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?

Indicates it requires human approval and is the sole path to confirmed status, but does not explicitly contrast with sibling tools like takeover_verify or takeover_detect.

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