reinvent_attach_pid

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 adds meaningful context beyond the obvious: the server uses os.kill(pid, 0) to check if the process is running, and the tool improves polling reliability. It could be more transparent about error handling or side effects (e.g., overwriting an existing PID), but the provided mechanism and rationale are strong.

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 compact and well-structured: a one-sentence purpose, a brief workflow explanation, and a small Args list. Every sentence adds value, and the first sentence front-loads the core function.

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 attach operation, the description covers the what, when, and why. It also gives the practical benefit (live polling reliability). It does not describe the return value or failure modes, which could be useful, but given the absence of an output schema and the tool's simplicity, the provided context is largely sufficient for an agent to select and invoke 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?

Schema description coverage is 0%, so the description must explain the parameters. The Args section defines job_id as 'Job ID from reinvent_register_job' and pid as 'Process ID of the running reinvent job', which adds meaning beyond the bare schema. It could be more detailed (e.g., formats or validation), but it clearly ties job_id to the upstream registration step.

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 tool's action: 'Attach a process ID to a registered user job for live polling.' This is a specific verb (attach), resource (process ID to job), and purpose. It distinguishes itself from siblings by referencing the workflow with reinvent_register_job and focusing on polling.

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 gives a clear 'when to use': after running a job manually and registering it with reinvent_register_job. It explains the benefit ('improving polling reliability') and mentions the server's os.kill mechanism. However, it does not explicitly state when not to use it or name alternative tools, so it stops short of a full 5.

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