check_system_health

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

No annotations are provided, so the description carries the full burden of disclosure. It states the tool 'checks' safety but does not explain what criteria define 'safe', what internal operations occur (e.g., reading sensors), or whether the tool has side effects. This is insufficient for an agent to understand the tool's behavior.

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, concise sentence that conveys the basic purpose. It is front-loaded and efficient, though it could be expanded slightly without losing conciseness. Score 4 for being appropriately sized.

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 the lack of parameters and output schema, the description should provide more context on expected output format or interpretation (e.g., returns true/false or a status). The agent is left unsure what 'safe' means or what the tool returns, making it less complete for effective use.

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 the schema coverage is 100% (empty schema). No additional parameter documentation is needed, so the description does not need to add parameter meaning. Baseline score of 4 applies.

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 workstation safety for heavy creative workloads. It uses a specific verb and resource, and the sibling tools list suggests this is a diagnostic tool, distinguishing it from action-oriented tools like throttle_process or prioritize_process.

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 usage when assessing readiness for heavy workloads, but it does not provide explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. Some inference is possible from sibling names, but no explicit advice is given.

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