delimit_semver

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

The description declares 'Side effects: read-only' and mentions the backend call 'backends.gateway_core.run_semver'. This provides key behavioral insight beyond what is in the schema or annotations. However, it does not detail error conditions or rate limits, but given the simplicity, this is adequate.

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 concise and well-structured: first sentence states purpose, followed by usage guidelines, sibling contrast, and side effects. No unnecessary information.

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 and the tool's straightforward nature, the description covers purpose, usage, side effects, and backend dependency. It is complete for effective use.

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 input schema has 100% description coverage, so the schema already documents parameters well. The description adds minimal extra context (e.g., 'optionally computing the next version string' for current_version), which does not significantly enhance understanding beyond the 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 clearly states the tool's purpose: 'Classify a spec change's semver bump (MAJOR/MINOR/PATCH/NONE).' It also distinguishes from siblings like delimit_diff and delimit_lint by specifying that this tool only maps the diff to a semver verdict.

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 when-to-use and when-NOT-to-use guidance, including alternative tool names (delimit_lint, delimit_diff). It also explains the optional computation of the next version string.

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