aap_add_host_to_group

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

Annotations indicate readOnlyHint=false and destructiveHint=false, and the description aligns by stating 'Add' and returning a JSON confirmation. However, the description does not reveal whether the operation is idempotent (e.g., what happens if the host is already in the group) or any error behaviors. It does not contradict annotations, but it adds limited behavioral context beyond the structured data.

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 short and includes an Args section and a Returns section, making the action and inputs clear at a glance. It is front-loaded with the main sentence, but the Args section slightly duplicates parameter descriptions already present in the schema. Overall, it is efficient and well-structured for a simple 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?

For a straightforward add operation, the description covers the action, parameters, and return type. It does not mention potential constraints such as requiring the host and group to be in the same inventory, nor error handling, but the operation's simplicity and non-destructive annotations reduce the need for extensive detail. The description is sufficient for an agent to invoke the tool with the correct IDs.

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 top-level input schema has a single 'params' object with 0% description coverage, but the description explains the nested structure and lists group_id and host_id with brief meanings. While the nested schema properties already have descriptions, the description clarifies the wrapping and provides a clear mapping to the expected input, adding value beyond the schema at the top level.

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 explicitly states 'Add an existing host to a group within an inventory,' using a specific verb and resource. This clearly distinguishes it from sibling tools like aap_remove_host_from_group, making the tool's purpose unambiguous.

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 gives some context by specifying 'existing host' and 'within an inventory,' implying prerequisites, but it does not explicitly compare to alternatives or state when to use this tool over others. No exclusions or sibling references are provided, though the purpose is straightforward enough for an agent to infer basic usage.

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