crystal_transient_lease

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

No annotations are provided, so the description carries the full behavioral burden. It lists three actions but does not disclose what 'clean' destroys, what 'promote' changes, whether leases expire, what permissions are required, or any side effects or reversibility constraints. This leaves major behavioral questions unanswered for a mutation tool.

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 a single, front-loaded sentence with no wasted words. It is concise, though its brevity contributes to the lack of actionable detail for a five-parameter mutation tool.

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 five parameters, three mutation actions, no annotations, and no output schema, the description is too thin. It does not explain the lease lifecycle, action-specific prerequisites, which parameters apply to which actions, or expected outcomes, leaving the agent to infer critical invocation details.

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 100%, so all five parameters are documented in the input schema, and the enum values are already fully specified. The description repeats the action names but adds no additional meaning about parameter interactions or expected values beyond the schema.

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 names the resource ('transient resource lease') and three operations ('create, clean, or promote'), so the general purpose is inferable. However, it does not explain what a transient lease is or distinguish this tool meaningfully from the many other crystal_* lifecycle tools beyond the resource name.

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?

There is no guidance on when to use this tool versus alternatives such as crystal_checkpoint, crystal_slice_fork, or crystal_melt. The action enum implies three possible uses, but the description does not state when each action is appropriate or what conditions should lead an agent to choose this tool.

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