create_system

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

No annotations are present, so the description must disclose behavioral traits. It only states 'Create a new system container,' which is a write operation, but does not mention side effects, permission requirements, or whether the creation is irreversible. The output schema exists but is not referenced.

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 single sentence is concise and free of fluff. However, it is slightly under-specified for a creation tool. It earns a 4 for being efficient but not wasting words.

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 tool's simplicity (3 parameters, simple creation), the description is minimally adequate. It does not explain what a 'system container' is in the context of the model, but the presence of an output schema reduces the need to describe return values. Overall, it meets basic requirements but leaves gaps.

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?

With schema description coverage at 67%, the description adds no parameter-specific meaning beyond the schema. For instance, 'server_version' lacks description in both schema and tool description, leaving its purpose unclear. The description does not elaborate on required parameters or their format.

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 'Create a new system container' specifies a clear verb ('create') and resource ('system container'), distinguishing it from sibling tools like 'delete_threat_model' or 'get_system'. It is unambiguous and directly states the tool's purpose.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., 'create_tag' or 'create_reliance'). The description lacks context on prerequisites, such as requiring an existing workspace, or scenarios where this tool is appropriate.

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