host_software_inventory_get

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 behavioral disclosure. The description only states what data is returned (software asset info) but does not disclose any behavioral traits such as whether the query is read-only, whether it requires specific permissions, whether it returns partial data if the host is not found, or any rate limits. For a read-like query tool, the lack of explicit read-only or error behavior disclosure is a gap.

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 front-loads the main purpose and lists the data categories. It is efficient and has no wasted words. It could be slightly improved by adding usage guidance, but for what it is, it is well-structured and 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 tool has one parameter, a clear schema, and an output schema, the description is mostly complete for a simple query tool. However, with no annotations and no mention of error behavior or permission requirements, an agent might not know how to handle cases like an invalid host_identifier or whether the tool is safe to call without side effects. The output schema exists, so return values are covered, but behavioral context is missing.

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%: the only parameter, host_identifier, is described as '主机标识（hostid/IP地址/主机名）' (host identifier: hostid/IP/hostname). The description adds the context that this parameter identifies a single host, but it does not add meaning beyond the schema. Baseline 3 is appropriate since the schema already documents the parameter fully.

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 states a specific verb ('查询' = query) and resource ('单台主机的软件资产信息' = software asset information of a single host), and lists the specific data categories (software/software_full/software_app_a-e). It is clear about what the tool does, though it does not explicitly differentiate from siblings like host_get or item_get, which are broader host-related tools.

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: use this tool when you need software asset information for a single host. It does not explicitly state when not to use it or mention alternatives (e.g., use host_get for general host info, or hostgroup_get_hosts for multiple hosts). The context is clear enough for a single-host query, but no exclusions or alternative routing are provided.

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