wazuh_get_group

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

The description uses 'get' which implies read-only, but it does not explicitly state that this is a read-only operation with no side effects. Since no annotations are provided, the description should more clearly disclose the read-only nature to aid safe agent usage.

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 of 15 words, directly stating the tool's purpose and what it returns. No unnecessary words or redundant information.

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?

The description mentions the returned details (configuration and member agents) and, combined with the output schema, provides sufficient context. It does not mention prerequisites like group existence, but the simple parameter and output schema mitigate the need.

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 input schema provides 100% coverage for the only parameter (group_id) with a clear description and examples. The tool description does not add any additional parameter information beyond what the schema already provides.

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 it gets detailed information about a specific agent group, including configuration and member agents. This distinguishes it from siblings like wazuh_list_groups (list all groups) and wazuh_group_agents (list agents in a group), as it provides a single group's full details.

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?

While the description implies this tool is for detailed group info, it does not explicitly state when to use it versus siblings like wazuh_list_groups for overviews or wazuh_group_agents for agent lists. No usage prerequisites or exclusions are mentioned.

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