check_database_freshness

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

The readOnlyHint annotation already indicates a safe read operation, so the description adds value by disclosing the 24-hour staleness threshold and the SUSE-only limitation. It also clarifies that the tool only warns (does not auto-refresh), which is a useful behavioral trait beyond the annotation.

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 description is three sentences, includes a useful [MAINTENANCE] tag at the start, and contains no filler. Every sentence contributes to understanding the tool's purpose, constraints, and usage context.

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 simple tool with no parameters and no output schema, the description adequately covers what it does, when to use it, and its OS limitation. It doesn't mention the exact output format (e.g., timestamp or status message), but this is not critical for selecting/invoking the tool, especially given the simplicity.

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?

With zero parameters in the input schema, the baseline is 4. The description does not need to explain parameters since none exist, and it correctly refers to 'package databases' as the target without implying any configurable options.

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 clearly states the tool checks when package databases were last synchronized and warns if they are stale (> 24 hours). This specific verb+resource combination distinguishes it from siblings like check_updates_dry_run and verify_package_integrity, making its purpose unambiguous.

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?

The description provides an explicit 'When to use' section ('Check if zypper cache is stale and needs zypper refresh'), which gives clear context. It also notes the SUSE Linux restriction. However, it does not explicitly mention when not to use it or name alternative tools, so it loses a point for lacking exclusions.

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