tealfabric_create_webapp_version

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

No annotations are provided, so the description carries the full burden. It does add real value by disclosing that the operation copies the latest version and that the result is unpublished (not live), but says nothing about permissions, whether the source webapp's state changes, or what the call returns.

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?

One short sentence with the key constraint ('unpublished') and the copy behavior front-loaded. Nothing is wasted and nothing important is buried.

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 one-parameter create tool with no annotations or output schema, the description covers what it does but omits what the caller gets back (new version identifier?) and any precondition such as an existing version to copy. Adequate but with clear 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?

There is a single parameter with 100% schema coverage ('Webapp UUID'), so the schema already carries the semantics. The description adds no further detail about the identifier (e.g., where to obtain it or that it refers to the source webapp being copied). Baseline 3 applies.

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?

States a specific verb and resource ('Create a new ... version of a webapp') and scopes it with 'unpublished' plus the copy semantics in parentheses. It implicitly contrasts with tealfabric_create_webapp and tealfabric_publish_webapp, but never names those siblings, so an agent must infer the distinction.

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 implies the usage case (you want a draft copy of the current version before editing), but gives no explicit when-to-use/when-not guidance and no mention of alternatives such as create_webapp or update_webapp. Usage is inferred from the word 'unpublished' rather than stated.

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