create_lab

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It states the lab is 'empty' but does not mention prerequisites, duplicate-title behavior, persistence, permissions, or any side effects. For a mutation tool, this is a significant gap.

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 exactly two sentences: the first states the primary function, the second gives immediate follow-up actions. Every word adds value, with 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?

The tool is simple (2 string parameters) and there is an output schema, so return value documentation isn't needed. The description covers the purpose and how to populate the lab. However, it omits important edge-case behavior like duplicate titles or failure modes, making it minimally adequate but not complete.

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 has only 2 parameters with 0% description coverage, and the description provides no parameter information whatsoever. It does not explain that 'title' is required, what 'description' is for, or the default behavior. The description entirely fails to compensate for the schema's lack of semantic explanation.

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 ('Create a new, empty lab') and clearly distinguishes this tool from siblings like 'delete_lab', 'start_lab', and 'list_labs'. It also states the result is an empty lab, which sets it apart from topology modifications.

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 explicitly recommends using 'add_node/add_link or build_topology' to populate the lab, giving clear next-step guidance. It doesn't explicitly state when not to use this tool, but there are no reasonable alternatives for creating a lab, so the guidance is sufficient.

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