waf_check_request

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

No annotations are provided, so the description must carry the full burden. It discloses that the tool returns an alert list (or empty list) and implies it is a read-only check. However, it does not mention side effects, authentication needs, or rate limits. The behavioral coverage is adequate but not comprehensive.

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 very short (two sentences) and front-loaded with the main purpose. It contains no unnecessary words. However, it could be improved by structuring parameter details more clearly.

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 5 parameters, no schema descriptions, no annotations, and an output schema (not detailed), the description is incomplete for an AI agent to use correctly. It lacks parameter explanations and does not cover how to structure requests. The url tip is helpful but insufficient.

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 0%, yet the description only elaborates on one parameter: 'url 建议包含完整查询串'. It does not explain the meaning or expected format of method, headers, body, or cookies. The description adds little beyond the schema property names, leaving the agent to infer common HTTP semantics.

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 action: '对 HTTP 请求做 WAF 规则检测' (perform WAF rule detection on HTTP request) and specifies the output: '返回命中的告警列表' (return list of matching alerts). It distinguishes itself from sibling tools (waf_reload_rules, waf_rule_stats, waf_run_self_tests) which focus on rule management.

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 includes a usage tip: 'url 建议包含完整查询串' (url is recommended to include full query string), but does not explicitly state when to use this tool vs alternatives or provide any exclusions. The context implies it is for checking a single request, but guidance is minimal.

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