system_health_check

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

No annotations are provided, so the description bears full responsibility. It explicitly says 'inspects' (not modifies or deletes), and outlines three specific areas (capability readiness, storage, chain-of-custody). This is transparent about the non-destructive, read-only nature of the tool.

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 a single sentence with 13 words, front-loading the key verb 'inspects' and then listing the three areas. There is no waste; every word contributes to the 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?

The description covers the tool's purpose and scope sufficiently for a zero-parameter, read-only health check tool. The output schema exists but the description doesn't need to explain return values. It could mention that the output schema details the health status, but overall it's complete for the tool's 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?

Schema description coverage is 100%, and there are zero parameters. The description doesn't need to elaborate on parameters since there are none, but it does explain what the tool inspects, adding value beyond the empty schema.

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 it inspects 'real-time host forensic capability readiness, storage, and chain-of-custody status'. This provides a specific verb ('inspects') and a noun ('host forensic capability') that distinguishes it from sibling tools like scan_iocs or extract_metadata.

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 implies this is a diagnostic/readiness check for forensic hosts, distinct from sibling tools that deal with extracted data or IOCs. It doesn't explicitly state when not to use it, but given its clear purpose and the zero-parameter input, the context is well-understood.

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