wazuh_sca_checks

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It only states that the tool returns check results with filtering, but does not mention whether it is read-only, authentication requirements, rate limits, or data freshness. The read-only nature is implied but not explicitly confirmed, which is a gap for a query tool.

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, clear sentence that is front-loaded with the primary action. It contains no redundant words or information, earning its place by succinctly conveying functionality and key filtering options.

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?

Given that the tool has an output schema (not shown but indicated), return values are already documented. With 6 parameters all described in the schema, and the tool description covering the main filtering options, the description is complete enough for a query tool. A score of 5 would require explicit usage timing or integration hints, which are absent.

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 description coverage is 100%, so the baseline is 3. The tool description adds a summary of filtering capabilities ('Filter by policy, search, or result status'), which aligns with the schema descriptions but does not add new meaning beyond them. The schema already adequately documents all parameters, including default values and types.

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 retrieves SCA check results for an agent, with filtering by policy, search, or result status. The verb 'Get' and resource 'SCA check results' are specific, and it distinguishes from sibling tools like 'wazuh_sca_status' which deals with policy-level status.

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 detailed compliance checks, but it does not explicitly state when to use this tool versus alternatives like 'wazuh_sca_status' or 'wazuh_compliance_report'. No 'when not to use' guidance is provided, leaving the agent to infer context from sibling names.

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