rush_scan_handoff

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

With no annotations, the description carries the full burden of behavioral disclosure. It suggests an action with side effects ('acknowledge', 'dispatch') but does not state what changes occur, whether the handoff consumes or locks resources, or what acknowledgment entails.

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 a single concise sentence and is not bloated, but the brevity comes at the cost of substance. It is readable yet under-informative, offering no structure or elaboration that would help an agent act.

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?

The tool has an opaque nested request object, no annotations, and no parameter or behavior explanations. The output schema may exist, but without input semantics or usage context an agent cannot reliably invoke this tool.

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 single 'request' parameter is an arbitrary object with additionalProperties true and 0% schema coverage, yet the description provides no information about its expected shape, fields, or meaning. The agent has essentially no guidance for constructing a valid request.

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 clear operation: preparing, dispatching, and acknowledging a bounded agent handoff of scan findings. It identifies both the action and the resource, and it is distinguishable from siblings like rush_scan or rush_agent_connection, though 'bounded' is not elaborated.

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 guidance on when to use this tool versus alternatives, no exclusions, and no mention of prerequisites. The phrase 'of scan findings' implies a context, but an agent gets no help deciding between this and related tools such as rush_scan or rush_context_pack.

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