ingest_handoff

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

No annotations are provided, so the description must carry the full burden. It discloses that the tool creates both a listener and a beacon and honors the noise ceiling. However, it does not mention potential side effects (e.g., overwriting existing listeners) or required permissions.

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 two sentences long with no wasted words. The first sentence front-loads the purpose, and the second provides key details. Every sentence earns its place.

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 single parameter and no output schema, the description explains the input format and process. However, it lacks information about the output (e.g., how to reference the created listener/beacon) and error conditions.

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 for 'handoff_data' is a bare object with no property descriptions. The description adds significant value by listing accepted keys (redirector, callback_domain, domain, lhost, host, hosts, protocol, port, os, arch). This compensates for the 0% schema coverage.

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 action ('stand up') and the resource ('listener + beacon from a p0rtix/msf-style handoff'). It distinguishes itself from sibling tools like 'start_http_listener' or 'generate_beacon' by specifying the unique input format.

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?

The description specifies when to use this tool ('from a p0rtix/msf-style handoff') and lists the accepted keys. It does not explicitly mention when not to use it, but the specialized nature implies clear usage boundaries.

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