gpt56_pro_followup

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

With no annotations, the description carries the burden and it discloses key behavior: the operation is queued (non-blocking), returns a child jobId, and requires verification. It also tells the agent the next step (poll status). It stops short of describing error/failure behavior, but the core behavioral contract is transparent.

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, front-loaded with the action and target, with the second sentence covering the return and polling behavior. No filler or repetition.

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 two-parameter tool with no output schema, the description supplies the preconditions, the return value, and the follow-up polling action. It is slightly thin on failure/error conditions, but complete enough for an agent to invoke and process the result.

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?

Schema coverage is 100%, so both jobId and prompt are already documented. The description restates the recency constraint for jobId ('latest completed round') and frames prompt as a follow-up task, reinforcing but not adding meaning beyond the schema. Baseline 3 is appropriate.

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 a precise action (queue a follow-up) and a specific resource (verified Quick Chat thread), clearly differentiated from siblings by emphasizing the same thread and returning a child jobId. It also names the polling sibling, so an agent can distinguish from gpt56_pro_start and gpt56_pro_status.

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?

Gives explicit preconditions: the target must be the latest completed round and must have a captured chat title, and directs the agent to poll gpt56_pro_status. It does not explicitly name gpt56_pro_start as the alternative for new threads, but the phrase 'follow-up in the verified same Quick Chat thread' strongly implies it.

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