add_wip_controller

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

With no annotations provided, the description fully discloses key behaviors: blocking (not rejection) when limit reached, the need for a return loop via connect_wip_return, and the fact that entities continue to flow after recycling a slot. This meets the high burden of transparency.

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 well-structured with sections (definition, structure, use cases) and front-loaded with the core purpose. It is slightly verbose but every sentence contributes value; no redundancy.

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?

Given the two parameters, existence of an output schema, and the tool's moderate complexity (WIP limiting with return loop), the description covers all essential aspects: purpose, behavior, structure, integration with other tools, and use cases. No critical gaps remain.

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 description explains that 'wip_limit' controls the maximum simultaneous entities, adding context beyond the schema's default and type. The 'name' parameter is implied from the function name but not explicitly described. Since schema coverage is 0%, the description adds meaningful clarification for one of the two parameters.

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 as a 'WIP (Work In Progress) limiter — Kanban / CONWIP entry gate', specifying it limits entities to a given limit via an entry gate. This distinguishes it from sibling tools like add_controller or add_buffer, which have different purposes.

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 provides concrete use cases (CONWIP production lines, Kanban pull, pipeline stages, thread pool) and advises to call 'connect_wip_return' after wiring. While it lacks explicit 'when not to use' guidance, the use cases and structural explanation effectively guide the agent.

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