hot_cache_status

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

With no annotations, the description carries full burden. It discloses that results are sorted by hot_score, lists all returned metrics with meanings (hits, misses, evictions, promotions, effectiveness, avg_hot_score). No contradictory or unexpected behavior implied. Lacks mention of potential latency or data freshness.

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?

Very concise: one sentence for purpose, then a bullet list of returned fields. Every sentence adds value. Front-loaded with main purpose.

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?

Given 0 parameters and no annotations, the description fully covers what the tool does and returns. With an output schema (implied), the description explains the structure adequately. No gaps for this simple tool.

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 has 0 parameters, so baseline is 4. Description adds value by detailing what the output contains, which is useful given no input parameters. It compensates for lack of schema complexity.

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 'Show current hot cache contents, stats, and observability metrics.' It uses a specific verb ('show') and identifies the resource ('hot cache') with distinct content (stats, metrics). This distinguishes it from sibling tools like predictive_cache_status and memory_stats.

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?

No guidance on when to use this tool vs alternatives. The description only explains what it does, not when to choose it over siblings like metrics_status or predictive_cache_status. No when-to-use or when-not-to-use information.

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