inventory-parse

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

No annotations are provided, so the description carries the full burden. It discloses that 'project_root sets CWD and uses ansible.cfg if present' and that 'deep is a placeholder; ignored for now.' However, it doesn't explicitly state whether the operation is read-only, destructive, or requires authentication. The merging behavior is mentioned but lacks detail on side effects.

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 concise: a one-line summary followed by a structured Args list. Each sentence earns its place, with no fluff. The information is front-loaded and easy to scan.

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?

With 5 parameters and an output schema present, the description covers the purpose and parameter semantics well. However, it lacks details on the output format (e.g., JSON structure of parsed inventory), error handling, or prerequisites like Ansible installation. The return type is assumed from the output schema, but a brief mention would improve completeness.

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%, so the description compensates fully. Each parameter is explained clearly: 'project_root' sets CWD, 'ansible_cfg_path' overrides, 'inventory_paths' supports ini/yaml/no-ext, 'include_hostvars' controls output, and 'deep' is a placeholder. This adds substantial meaning beyond the plain schema.

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 'Parse inventory via ansible-inventory, merging group_vars/host_vars.' It uses a specific verb ('parse') and resource, and the merging detail adds value. Among siblings like 'ansible_inventory' and 'inventory-diff', this description distinguishes itself by focusing on parsing with variable merging.

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?

There is no explicit guidance on when to use this tool versus alternatives. While the description implies it's for parsing inventory, it doesn't explain when to choose it over 'ansible_inventory', 'inventory-diff', or other inventory-related siblings. No exclusions or use cases are provided.

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