waf_rate_rule_set

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

No annotations are provided, so the description must disclose behavioral traits. It notes reversibility (remove=true) and that the rule is rate-based with per-IP counting over 5-minute windows. However, it does not describe what modifications to the WebACL entail (e.g., effect on existing rules, potential to replace or append) or the full impact of the 'dangerous' label beyond asking for confirmation. Some important behavioral details are omitted.

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 three sentences, front-loads the primary action and purpose, and uses clear, direct language. Every sentence adds distinct value: purpose + durability metaphor, parameter explanation, and danger warning. No fluff or 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?

Given 7 parameters, no output schema, and no annotations, the description covers the main behavioral context: creation/removal, reversibility, rate basis, and danger. It lacks explicit mention of idempotence for rule_name (only in schema) and default action when remove=false. Overall, it provides sufficient context for an agent to use the tool safely, with minor remaining gaps.

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%, so the description's value is additive. It explains site as ARN/ALB/instance, limit as per-5-min-per-IP, uri_scope as optional prefix, and action as block/count meaning. This directly aids parameter selection beyond the schema's basic type/description. A higher score would require more complex relationships or corner cases.

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?

Description clearly states the core verb-resource pair: 'Create/attach (or remove) a WAF rate-based rule on a site's WebACL'. The phrase 'durable fix for a flood' provides a strong use-case signal. Among sibling tools, none target WAF rate rules, so it is well-distinguished.

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 traffic floods ('durable fix for a flood') and warns about danger ('confirm with the user first'), but it does not explicitly contrast with simpler alternatives like block_ip or explicitly state when not to use this tool. Usage context is present but exclusions and comparisons are missing.

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