packagekit_refresh_cache

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

With no annotations, the description must carry the safety profile. It says 'refresh' which implies modifying system state (likely requires root privileges), but it doesn't disclose potential side effects, whether it triggers network downloads, or if it requires elevated permissions. This is a gap for a system-level operation.

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 sentence, no fluff, directly states what it does and the method. The purpose is front-loaded in the first few words.

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?

The tool has a single optional parameter with good schema documentation, but no output schema. The description doesn't explain what happens when the refresh completes (e.g., returns void or a success indicator). For a simple tool, this might be sufficient, but given the system-level nature, a note on permissions or side effects would improve completeness.

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 schema has 100% coverage for the single parameter 'force', with a description 'Force download of all repository databases.' The description text adds the context that it's about refreshing the cache, but the parameter is already well-documented. The high schema coverage raises the baseline, so this is adequate.

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 states the verb 'refresh' and the resource 'package manager repository metadata cache' via PackageKit D-Bus, which is clear. However, it doesn't differentiate from siblings like packagekit_check_updates, which also deals with metadata, but the action (refresh cache vs. check for updates) is distinct enough.

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 or when-not-to-use guidance. It implies it's for refreshing the cache, but doesn't mention alternatives like packagekit_check_updates for just checking. Sibling names suggest checking updates is separate, but the description doesn't clarify.

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