artifact_verify_checksum_integrity

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

No annotations exist, so the description carries the full burden and does so well: declares 'Read-Only verification', 'Side Effects: None', and specifies the failure behavior ('Blocks deployment if tampering or corruption is detected'). Doesn't mention authentication or rate-limit needs, so not a 5.

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?

Front-loaded imperative sentence followed by Purpose/When to Use/Behavior/Side Effects/Args structure with zero filler. Slightly verbose with redundant restatement (the first sentence already implies the Purpose and Behavior blocks), but every section still adds signal.

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 needn't be described. For a 3-param read-only verification gate, the description covers what it does, when, side effects, and all parameter formats — minor remaining gap is what happens on mismatch beyond 'blocks deployment' (error vs. boolean result is delegated to the output schema).

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 0%, so the description must compensate — and it does, documenting all three parameters with format hints: remote path vs. full URL for artifact_path_or_url, '64-character SHA256 digest' for expected_sha256, and default value for session_name.

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?

Opens with a specific verb+resource ('Compare the SHA256 digest... against registry checksum') and names the concrete sources (GitHub Actions/jenkins-mcp, Nexus/Artifactory). Clearly distinct from siblings like artifact_upload_binary or artifact_promote_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?

Explicitly states 'When to Use: In CI/CD pipelines right before deployment to Kubernetes/OpenShift', which gives clear context. It doesn't name a sibling alternative or state when NOT to use it, keeping it short of a 5.

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