Manage Script Version

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

Annotations already indicate this is a non-read, non-idempotent, non-destructive operation. The description adds useful behavioral context by stating versions are immutable and cannot be modified after creation. However, it does not disclose output behavior, error conditions, or any side effects beyond version creation.

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 two concise sentences with no filler. The primary action is front-loaded, and the immutability caveat is placed in a separate clarifying sentence. Every sentence earns its place.

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 schema coverage, output schema presence, and annotations, the description is largely sufficient for a simple create-version tool. It clearly states what is captured and the immutability constraint. Minor missing context includes when to prefer this over related version/script management tools, but this is more of a usage guideline gap.

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 the schema fully documents all four parameters. The description adds no additional parameter-level meaning beyond confirming that the action is 'create,' which matches the schema's action description.

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 clearly states a specific verb and resource: 'Create immutable version snapshots of a script project.' It also clarifies the core behavior—capturing a snapshot of current script code—and distinguishes itself from read-oriented siblings like get_script_version.

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 explicit guidance is given about when to use this tool versus alternatives such as get_script_version, manage_script_content, or manage_script_project. The description implies a create operation but does not state exclusions or conditions that would route an agent to the correct sibling.

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