get_next_version

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

With no annotations, the description should disclose behavioral traits such as side effects or state reads. It only says the tool calculates a version, which implies a read-only operation, but it does not explicitly confirm this or mention any dependencies like the store being initialized.

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 a single, concise sentence that front-loads the core action. It contains no redundant words or irrelevant details, making it highly efficient.

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, but the description lacks essential context: it does not explain what the 'highest store version' refers to, how the mode influences the result, or when to invoke this tool in a changelog workflow. The output schema exists but the surrounding semantics are insufficient.

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?

The schema documents a single 'bump' parameter with enum values and a default, but schema description coverage is 0%. The description mentions 'Modus' (mode) but does not explain how major/minor/patch affect the calculation, leaving the parameter semantics unclear.

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 the tool's function: 'Berechnet die nächste Version aus der höchsten Store-Version und dem Modus' (calculates the next version from the highest store version and the mode). This specific verb+resource distinguishes it from siblings like get_current_version and create_release.

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 guidance is provided about when to use this tool versus alternatives. It does not mention any prerequisites, exclusions, or scenarios where get_next_version is preferred over other version-related tools.

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