Unfour System Health

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint information, and the description aligns with those by saying it only returns readiness. It adds that the scope covers command-bus and storage, which is useful context. It does not add further behavioral detail, but the annotations and output schema reduce the burden on the description.

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 front-loaded sentence that communicates the main purpose efficiently. Some words, such as 'through the Unfour command bus', are slightly redundant with the tool name and title, but overall it is economical.

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 zero-parameter, read-only, idempotent tool with annotations and an output schema available, the description is complete enough for an agent to select and invoke it correctly. It clearly identifies the health-check purpose and the primary domains covered.

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 tool has zero parameters and an empty input schema, so there are no parameter semantics to document. The description does not need to explain parameters, and the schema fully captures the interface.

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 that the tool returns command-bus and storage readiness, and the title 'Unfour System Health' reinforces that it is a health/diagnostics check. It is distinguishable from sibling tools such as unfour.ssh.run_diagnostic and unfour.db.test_connection. It is clear but does not fully explain what 'readiness' means or what form the data takes.

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 phrase 'for diagnostics' implies that this tool is appropriate for diagnostic use cases. However, it does not explicitly say when to use this tool versus other diagnostic sibling tools like unfour.ssh.run_diagnostic or unfour.db.test_connection, nor does it state any exclusions. The usage context is implied rather than stated.

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