verify_catalog

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

Annotations already declare readOnly/idempotent/non-destructive with a closed world, so safety is covered. The description adds the substance of the checks (trusted hashes, orphan weights), though the word 'refresh' sits awkwardly against readOnlyHint and could make an agent wonder whether it mutates the installation record.

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?

One tight sentence with the actions front-loaded and no filler. It is perhaps too compressed — three distinct checks crammed into a clause list with no grouping or outcome framing.

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 no explanation, and there are no parameters to document. What is missing is the relationship to siblings and the failure semantics (what 'orphan weights' means for the caller, whether remediation is expected).

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?

Zero parameters, so the schema has nothing to explain and the description need not compensate. The baseline of 4 applies; the description correctly implies a whole-catalog, no-argument operation.

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 names three concrete activities (refresh installation state, check trusted hashes, report orphan weights), which is more specific than the tool name alone. But 'verify_catalog' versus the sibling 'refresh_catalog' is not distinguished, and 'refresh installation state' duplicates what a sibling name suggests, leaving the actual verification scope ambiguous.

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 indication of when to call this versus refresh_catalog, verify_audio, or check_update — all plausible neighbors in the sibling list. The agent has to guess whether this is a pre-download integrity check, a post-install validation, or a maintenance sweep.

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