wazuh_get_agent

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 states it gets detailed information but does not disclose behavioral traits such as whether it mutates state, required permissions, error handling for invalid agent IDs, or rate limits. Limited 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?

Single sentence, efficient, front-loaded with the verb 'Get'. Every word adds meaning, no redundancy.

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 simple get-info tool with an output schema, the description is sufficiently complete. It covers the key aspects of what is retrieved. Could briefly mention that response details are in the output schema, but not necessary.

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 coverage is 100% (one required parameter with description). The description adds value by listing the types of information returned (configuration, OS details, etc.), which goes beyond the schema's description of agent_id.

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 the tool's function: 'Get detailed information about a specific agent' and lists specific data categories (configuration, enabled modules, OS details, group membership, connection history). This distinguishes it from siblings like wazuh_list_agents (which lists agents) and wazuh_agent_health (likely health-focused).

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 implies usage for retrieving detailed agent info but does not explicitly state when to use this tool versus alternatives like wazuh_agent_health or wazuh_list_agents. No exclusions or prerequisites are mentioned.

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