tenki_create_volume

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

Annotations already indicate this is a non-read-only, non-idempotent, non-destructive action. The description adds useful behavioral context: the volume persists across sandbox teardown and is workspace-scoped, with workspace defaulting to the API key's first workspace. This clarifies the side effect without contradicting annotations.

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?

Two sentences with no fluff. The core action and persistence property are front-loaded, and the workspace default behavior is stated clearly in the second sentence.

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 three-parameter create tool with strong annotations, the description covers purpose, persistence behavior, and workspace selection. There is no output schema, so mentioning the return value would be helpful, but the description is otherwise sufficient for an agent to select and invoke the tool 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?

All parameters have full schema descriptions (100% coverage), so the baseline is 3. The description's mention of workspace_id defaulting overlaps with the schema's own workspace_id description, adding little new semantic value beyond reinforcing workspace scoping.

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 states a specific verb and resource: 'Create a workspace-scoped persistent volume.' It also defines the key differentiator—durable block storage that survives sandbox teardown—so an agent can distinguish this from sandbox, snapshot, and template creation tools.

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 clear context for when the tool is appropriate: when persistent block storage that outlives sandbox teardown is needed. It does not explicitly name sibling alternatives or state when not to use it, so it does not earn a full 5.

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