verify_provenance_integrity

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

With no annotations, the description carries the full disclosure burden. It says a hash chain is re-walked and breaks reported, but never states whether the operation is read-only, what a 'break' result looks like, or whether it needs prior provenance entries. The pricing block confusingly implies a tier requirement with feature claims that do not apply to this tool.

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 first sentence is tight and front-loaded, but the following three sentences are pure marketing boilerplate for Kiln Pro that waste space and introduce false associations with calibration and decoration features.

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 zero-parameter verification tool with no output schema, the description should explain what the returned report contains and what counts as a break. Instead it spends its length on an upsell, leaving the actual behavior underspecified.

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 tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. It correctly presents the tool as taking no input arguments.

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 opening clause names a specific verb and resource: re-walk the provenance log's hash chain and report breaks. However, the remaining three lines describe printer calibration, textures and decorations, which have nothing to do with hash-chain verification and actively muddy what the tool does. No differentiation from near siblings such as verify_audit_integrity, verify_design_release or get_provenance_history.

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 statement of when to run this versus get_provenance_history, verify_audit_integrity or the various release-verification tools. The only additional text is an unrelated upsell, which gives no usable selection criteria.

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