check_package_compatibility

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds one genuinely useful disclosure — 'installation is untested' — clarifying this is a static constraint evaluation, not a real install simulation. It stops there, saying nothing about whether dependency resolution is recursive, whether network/CRAN access occurs, or what happens when the R version is invalid.

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?

A single front-loaded sentence with no filler; the key caveat is placed after the semicolon where it reads as a qualifier rather than a headline. It is not padded, though the terseness borders on under-specification rather than crispness.

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?

An output schema exists, so return values need not be explained, but a three-parameter tool with 0% schema description coverage and no annotations about network or resolution behavior needs far more from the description. The unexplained bioc_version parameter alone is enough to leave an agent guessing on a required-ish input.

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 description coverage is 0%: none of the three parameters (package, r_version, bioc_version) carries any documented meaning. The description only obliquely gestures at version checking and never explains the expected format of r_version, whether package takes a name or name@version, or what bioc_version controls. With full burden on the description, this is a significant gap.

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 verb 'Check' plus the resource 'compatibility' is identifiable, and the description narrows scope to the R/release version and direct required dependency constraints. However, phrasing like 'R/release' is compressed shorthand, and it never states in plain terms whether the check covers a package's declared version requirement vs. its dependencies' requirements. It is distinguishable from check_package_version only by inference.

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?

There is no explicit when-to-use guidance, no prerequisites, and no mention of alternatives despite close siblings such as check_package_version, get_dependencies, and get_bioconductor_version. The agent must guess whether to run this before or instead of those tools.

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