check_version_compatibility

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

Annotations only declare readOnlyHint and openWorldHint, so the description must carry the rest, and it does: it discloses that v1 coverage is intentionally bounded, that matrices are not scraped at runtime and require manual refresh via compat-matrices.json, and that limitations surface in notes[]. That is meaningful behavioral context beyond the annotations, though it does not discuss auth or rate limits.

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 purpose is front-loaded in the first sentence, followed by the numbered validation list and the scope caveat. Dense but every sentence carries information; the numbered clauses are slightly long but earn their place.

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?

For a multi-check validation tool with an output schema already present, the description covers what is validated, the conditional triggering of each check, the static-matrix limitation, and where limitations are reported (notes[]). Nothing needed to call it correctly is missing.

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 coverage is 100%, so the baseline is 3, but the description adds real semantic linkage beyond the schema: it explains that springBoot expands the BOM and enables javax→jakarta checks at ≥3.0.0, and that android versions are validated against shipped matrices. It clarifies cross-parameter effects the schema only hints at.

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?

States a specific verb and resource ('Check whether a set of versions is mutually compatible') and then enumerates the three distinct validations it performs (Spring Boot BOM, AGP↔Gradle↔JDK/KGP matrix, javax→jakarta). This clearly separates it from siblings like check_multiple_dependencies or check_version_exists, which only test existence.

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 explains conditional activation ('when springBoot is set', 'when Spring Boot ≥ 3'), which implies usage context, but it never explicitly says when to prefer this tool over siblings such as detect_dependency_conflicts or check_multiple_dependencies, nor does it name any alternative. Usage is inferred rather than directed.

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