createVersion

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

Annotations only include readOnlyHint=false, which already indicates a write operation. The description adds no further behavioral context—no side effects, required permissions, implications for existing data, or response details. Since the description is so minimal, it fails to carry the burden of behavioral disclosure.

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?

While 'Create version' is extremely short, this is under-specification rather than conciseness. The description has no structure, no key information, and is effectively a placeholder. It does not earn its place because it communicates nothing beyond the tool name.

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?

The tool involves a complex nested schema with multiple optional fields, no output schema, and minimal annotations. The description is completely inadequate for an agent to understand how to call it correctly, what parameters are required, or what constitutes a valid request. It fails to provide any of the context necessary for correct invocation.

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 0%, and the description does not explain any of the parameters. The schema contains many nested fields (name, status, sharing, due_date, etc.) and path params (format, projectId), but the description provides no hints about their meaning, format, or usage. The agent is left entirely to infer from raw JSON 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 'Create version' states a clear verb and resource, which is enough to distinguish it from other create tools like createIssue or createProject. However, it lacks any detail about what a version is in this context or what the tool specifically does beyond the literal name, so it's minimally adequate but not informative.

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 like updateVersion or deleteVersion. It doesn't mention contexts, prerequisites, or related operations. The description provides zero usage direction.

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