host_ops

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds a return envelope and two result shapes, but the example host_ops(operation="get_system_info", detailed=True) references a parameter absent from the schema, which can mislead invocation.

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 sectioned and front-loads the host-context purpose, but the 12-operation list duplicates the enum in the schema, 'Args: See Parameters block' is wasted text, and the invalid example consumes space without helping invocation.

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?

This is a complex 12-operation dispatcher with four undocumented parameters and substantial sibling overlap, so the description needs more parameter and selection context. Output schema exists, so return values need not be fully explained, but the missing per-parameter semantics and alternative guidance leave it incomplete.

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 0% for four parameters, and the description punts with 'Args: See Parameters block.' It gives one category example for get_help but never defines level, tool_name, or the meaning/range of category, and the detailed=True example is not a valid parameter.

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 names host system context and enumerates the specific get_* operations, so the agent can tell it retrieves host information. It does not differentiate these operations from overlapping monitor_* siblings such as monitor_get_system_status and monitor_get_cpu_info.

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 provides no when-to-use or when-not-to-use guidance, and it never mentions the monitor_* alternatives that retrieve similar system data. The examples show invocation syntax for two operations but do not explain selection criteria.

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