homebutler

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

No annotations provided, so description carries full burden. 'Get' implies read-only operation, but description omits permissions required, error behavior if server unreachable, performance characteristics, or whether this executes local system commands.

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?

Single concise sentence of 9 words. Front-loaded with action and resource, zero redundancy. Efficiently lists return metrics without verbose elaboration.

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?

Simple tool with adequate coverage for basic invocation. Lists returned metrics compensating for missing output schema, though could benefit from mentioning return format or error conditions given lack of annotations.

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 100% description coverage for the single optional 'server' parameter. Description mentions none of the parameters, but baseline is 3 when schema is fully self-documenting.

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?

Clear verb 'Get' with specific resource 'system status' and enumerated metrics (CPU, memory, disk, uptime). Distinguishes implicitly from siblings by focusing on host-level metrics, though lacks explicit differentiation from docker_list or install_status.

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 versus alternatives like docker_list (container status) or install_status (application status). No preconditions or 'when-not-to-use' advice provided.

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