create_version

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

No annotations are provided, so the description carries the burden. It states the core behavior ('Create a new version') and adds domain context, but it does not disclose permissions, idempotency, duplicate-name behavior, or response format. This is adequate but not rich.

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 front-loaded with the action, followed by a concise purpose statement and a tight bullet list of use cases. Every sentence earns its place; there is no filler or redundancy.

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 6-parameter creation tool with no output schema, the description provides enough context to understand the tool's role and typical use. It omits return-value details and edge-case constraints, but the schema covers parameter validation and the use cases cover selection intent.

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 already documents all 6 parameters. The description adds value by framing 'Set version owners and dates' as a use case, which gives semantic context to owners, startDate, and publishDate beyond their raw schema descriptions.

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 opens with a specific verb+resource: 'Create a new version in a Yunxiao Project.' It clearly distinguishes this creation tool from sibling tools like update_version, delete_version, and list_versions by emphasizing 'new version' and adding domain purpose (release plans, delivery progress).

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 'Use Cases' section gives clear context for when to create a version: new release version, project milestones, setting owners/dates. It does not explicitly mention alternatives like update_version for modifying existing versions, but the creation context is unambiguous.

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