List product versions

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

Annotations already declare readOnlyHint=true, so the safe read behavior is known. The description adds no behavioral context beyond that; 'Version.filter.' is obscure and the requirement note does not explain how the tool behaves internally or what it returns. Thus it fails to meaningfully enhance transparency.

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 very short and the second sentence about being required for TestPlan.create and Build.create is valuable. However, the first sentence 'Version.filter.' is a cryptic fragment that adds little value and is not well structured, so it is not concise in an effective way.

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 is simple with three documented parameters and no output schema. The description provides important dependency information but does not explain the return structure or filtering behavior beyond the schema. It is adequate but leaves gaps for an agent unfamiliar with Kiwi.

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?

All three parameters (limit, query, product) have schema descriptions, covering 100% of the parameters, so the description does not need to repeat them. The description adds no additional parameter-level detail, yielding a baseline score of 3.

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 title 'List product versions' clearly states the purpose, and the description adds that it is a version filter required for creating test plans and builds. However, 'Version.filter.' is a cryptic fragment that lacks a clear verb, and no explicit distinction from sibling list tools is made.

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 provides explicit context by stating it is required for TestPlan.create and Build.create, telling the agent when to use this tool. It does not mention alternatives or exclusions, but there are no direct sibling tools for listing versions, so this is sufficient.

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