check_health

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

Discloses non-read-only nature via auto-repair mention, consistent with annotations. Provides detail on checks and return of storage stats. No contradictions.

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?

Two sentences with a list of checks. Front-loaded with purpose. Could be more structured (e.g., separate list), but no unnecessary 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?

No output schema; description only says 'Returns storage stats' without details on format or how to interpret health results. For a diagnostic tool covering 16 checks, more context on output would be beneficial.

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 coverage is 100% with clear parameter descriptions. The tool description reiterates agent_id scope and fix behavior but adds no new semantics beyond what the schema provides.

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?

Description clearly states the tool checks memory database health with 16 specific checks, and distinguishes it from siblings like deep_check by listing detailed issues. Verb 'Check' plus resource 'memory database health' is specific.

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?

Usage is implied: use when you need to assess health and optionally repair. No explicit when-not or alternatives, but the description gives purpose. Could be improved by contrasting with deep_check.

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