Trigger a FIM or SCA scan

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

The description discloses key behavioral aspects: it triggers a write operation, requires write permission, and places load on endpoints. The annotations already indicate readOnlyHint=false and idempotentHint=false, and the description aligns with those without contradiction.

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 compact and front-loaded, using two sentences to convey the purpose, timing, prerequisite, and operational impact. There is no redundant or filler content.

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 one-parameter action, the description provides the essential context: what triggers, when to use it, the required permission, and the side effect on endpoints. Output schema exists, so not describing return values is acceptable, though failure/response behavior could be slightly more explicit.

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 schema already provides a clear description for the agent_ids parameter, including the format and an example. The tool description reinforces the scan context but does not add substantial meaning beyond the schema's own parameter documentation.

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: to start a syscheck (FIM) scan immediately rather than waiting for the scheduled run. It also distinguishes this action from related read/search tools by identifying it as an on-demand scan operation.

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 explicitly says when to use the tool ('instead of waiting for the schedule') and notes the prerequisite WAZUH_ALLOW_WRITE=true. It also warns about load on target endpoints, giving the agent enough context to decide whether this action is appropriate.

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