inventory__get_host_details

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

Annotations declare readOnlyHint=true, and the description is consistent (get operation). Description adds specific return fields, enhancing transparency. No mention of limits or errors, but the simple nature of the tool (1 param, output schema) makes this acceptable.

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?

Description is concise (2-3 sentences) with a clear purpose statement followed by a bullet-like list of return data categories. Every sentence adds value, no redundancy.

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, an output schema exists, and annotations declare readonly, the description covers all necessary context: what it does, what it returns, and how to call it. The agent has sufficient information to select and invoke the tool correctly.

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 sole parameter (host_ids) is described in the schema as 'Comma-separated list of host IDs (UUIDs) to retrieve.' The description adds context by listing the expected fields in the response, which helps the agent understand the value of using this tool. With 100% schema coverage, baseline is 3; additional context raises to 4.

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?

Description clearly states 'Get detailed information for specific hosts by their IDs' and lists the types of data returned (identifiers, network info, cloud provider, etc.). This distinguishes it from sibling tools like inventory__find_host_by_name (search by name) and inventory__list_hosts (list with filters).

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?

Description implicitly tells when to use (when you have host IDs and need comprehensive details). It does not explicitly mention when not to use or compare to alternatives, but the sibling names provide context. A clear usage scenario is evident.

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