inventory__find_host_by_name

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

The annotations already include readOnlyHint: true, so the description's 'find' aligns with a safe read operation. However, it does not disclose additional behavioral traits like whether the search is case-insensitive, returns null vs error on no match, or supports full vs partial hostname. With annotations present, the description offers minimal extra transparency.

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, clear sentence with no wasted words. It is front-loaded and immediately informative, fitting the simple purpose of the tool.

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's simplicity (one parameter, a clear action, and an output schema), the description is mostly complete. It could mention that it returns host details or indicate if it supports partial matching, but the presence of an output schema reduces the need for return value explanation. Overall, adequate for a straightforward lookup.

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 parameter 'hostname' is fully described in the input schema (100% coverage) with description 'The hostname or display name to search for.' The tool description adds no additional meaning beyond what the schema already provides, so a baseline score of 3 is appropriate.

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 'Find a host by its hostname/display name,' specifying the verb (find) and resource (host) with the key attribute. This distinguishes it from sibling tools like inventory__get_host_details (which likely uses ID) and inventory__list_hosts (which lists all hosts).

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 guidance on when to use this tool versus alternatives like inventory__list_hosts or inventory__get_host_details. It does not state whether it performs exact match or partial search, nor does it mention limitations such as case sensitivity or result uniqueness.

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