get_agent_processes

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

No annotations exist, so the description must disclose behavioral traits. It only states 'List running processes' without mentioning whether the operation is read-only, what happens if the agent_id is invalid, or any side effects. The description fails to provide essential behavioral context beyond the basic action.

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 sentence that efficiently conveys the core purpose. While it is concise, it could benefit from slightly more structure (e.g., bullet points for parameters or usage context), but it remains straightforward and front-loaded.

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 no output schema, the description should hint at return values or pagination behavior. However, it only states the operation, leaving agents without clues about the response structure or how parameters like limit, offset, and search affect results. The description is incomplete for a tool with 5 parameters.

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 has 100% description coverage, so the schema already explains parameters. The description adds no additional semantics beyond the tool's high-level purpose, which is the baseline expectation.

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 purpose: listing running processes on a Wazuh agent. It uses a specific verb ('list') and resource ('processes'), and implicitly distinguishes from sibling tools like get_agent_network or get_agent_ports that deal with other data.

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?

No guidance is provided on when to use this tool versus alternatives. With many sibling tools listing different agent data, the description should indicate that this is for process monitoring, but it does not offer any exclusions or context about when not to use it.

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