inventory-find-host

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

No annotations are provided, and the description only hints at behavior with 'across the resolved inventories', but does not explain side effects, whether it's read-only, or any prerequisites. Minimal disclosure beyond the verb.

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, but it omits essential details. It is front-loaded but under-specified, balancing brevity against completeness.

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 4 parameters and the existence of an output schema, the description is insufficient. It does not explain how inventories are resolved, parameter behavior, or expected outcomes, making it hard to use correctly without additional knowledge.

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%, meaning the input schema has no descriptions for its 4 parameters. The description fails to compensate by explaining any parameter's purpose, leaving the agent to guess the role of 'host', 'project_root', 'inventory_paths', and 'ansible_cfg_path'.

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 'Find a host, its groups, and merged variables across the resolved inventories' clearly states the action (Find) and the resources (host, groups, merged variables). However, it does not explicitly differentiate from sibling tools like inventory-add-host or inventory-diff, which could be improved.

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, when not to, or alternatives. It simply states the function without context for decision-making.

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