gpt56_pro_start

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

With no annotations, the description carries the burden and discloses key behavior: immediate return with jobId, daemon serialization, UI verification, and external lifecycle state. It does not mention failure modes or idempotency, but the async nature and polling requirement are clearly conveyed.

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?

Three sentences each serve a distinct purpose: stating the action, describing the return behavior, and explaining daemon internals and next step. The key information is front-loaded, and there is 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 one-parameter async queue tool with no output schema, the description covers what to send, what is returned (jobId), and what to do next (poll status). It does not explicitly say how to use the jobId with siblings, but that is a minor inferable gap.

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 already documents the single 'prompt' parameter with a full description (100% coverage), so the baseline is 3. The tool description adds no new parameter-specific detail beyond the schema's own description, merely restating that the prompt is the task.

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 specific verb 'Queue' and a specific resource 'GPT-5.6 sub-agent job', making the tool's role clear. The phrase 'for this MCP workspace' scopes it further, and the sibling tools (status, followup) are implied to have different purposes. The description distinguishes this as the start action.

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 clear context that this queues a job and returns immediately, and instructs to poll gpt56_pro_status afterward. However, it does not explicitly compare to the followup sibling or state when not to use this tool, so usage is more implied than fully specified.

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