delimit_semver

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

With no annotations, the description partially covers behavioral traits: it states classification is deterministic and based on diff engine output, and optionally computes next version. However, it omits side effects, permission requirements, or error handling.

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 extremely concise with two sentences, efficiently stating the main purpose and key behavior. It is front-loaded and contains no extraneous text.

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?

Given the presence of an output schema, return values are partially covered. However, the description lacks context about the diff engine, how to ensure it is set up, and the format of the version string. For a tool without annotations, more detail would improve completeness.

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?

While the input schema has 100% coverage, the description adds meaning by explaining that old_spec and new_spec are paths to spec files for diff comparison, and that current_version is for optional next version computation. This contextualizes the parameters beyond 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 clearly states the tool's purpose: classifying semver bumps (MAJOR/MINOR/PATCH/NONE) for a spec change. It specifies the output and notes it's deterministic. This distinguishes it from sibling tools like delimit_diff, which likely produces raw diffs.

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 does not provide guidance on when to use this tool versus alternatives, nor does it mention prerequisite steps (e.g., needing diff engine output). There is no information about when not to use it.

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