follow_up

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

Given no annotations, the description carries the full burden. It discloses context preservation, immediate return (non-blocking), and the need to poll with `status`. It also states the pre‑condition (delegate finished). It doesn't cover error cases or side effects explicitly, but for this tool the key behaviors are well communicated.

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?

Two sentences pack purpose, usage, alternatives, and behavior with zero filler. The primary instruction (use for finished delegates) is front-loaded, and each clause serves a purpose.

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?

For a simple 2-parameter tool without an output schema, the description covers the essential workflow: when to use, what it does, and how to obtain results (poll via `status`). Minor gaps like error handling or repeated follow‑ups are not critical for an agent to call it correctly.

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 documents the `prompt` parameter, but `sessionId` is left undocumented. The description does not add explicit meaning for `sessionId` beyond the name and context. With 50% schema coverage, this is borderline; the description could have compensated by explaining that `sessionId` identifies the finished delegate session.

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?

Clear action (send another prompt) targeted at a specific resource (a finished delegate) while preserving context. Explicitly distinguishes from spawn and steer, making the tool's purpose unambiguous even among many siblings.

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?

Provides direct guidance to use this instead of spawning a fresh delegate, and explicitly directs to `steer` for a working delegate. The when-to-use and when-not-to-use conditions are spelled out, leaving no ambiguity.

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