pt_lab

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

The description explains that verify=true pings test pairs after convergence, which is useful behavioral context beyond the openWorldHint annotation. But for a lab-building mutation tool with no readOnly/destructive annotations, it omits important behavior such as what clear_first does, whether existing lab state is overwritten, and what happens on conflicts.

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 front-loaded with the core action and is dense with useful detail. The blueprint list is long but directly supports tool selection and parameter use, with no filler sentences.

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 complex lab-construction tool with no output schema and 0% schema description coverage, the description leaves key gaps: clear_first behavior, params syntax, and what happens to any existing lab. It provides enough to understand the high-level purpose but not enough to invoke the tool safely and correctly in all cases.

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 carry parameter meaning. It explains name='list' and lists blueprints, and explains verify=true, but it does not explain the params object structure or the clear_first parameter at all, leaving two of four parameters underspecified.

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 uses a specific verb and resource: 'Build a complete, pre-computed lab' and enumerates what is included (devices, cabling, IPs, configs, hosts, test pairs). The 'in one call' phrasing helps distinguish it from granular sibling tools, but it does not explicitly name or contrast with alternatives such as pt_build.

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?

It gives useful usage details for name='list' and verify=true, and implies the tool is for creating complete labs in one call. However, it does not state when to use this instead of pt_build or the more granular device/connection tools, nor does it mention exclusions or prerequisites.

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