bunny_manage_rate_limit_rule

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

Annotations already provide readOnlyHint=false and destructiveHint=true, and the description aligns by including 'delete.' It adds contextual value by explaining that rate limits block clients over a configured threshold, but it does not disclose side effects such as propagation timing, rule replacement behavior on update, or required permissions. This is adequate but not rich.

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?

Two sentences with no filler: the action is front-loaded, followed directly by the relevant rule-object fields and a one-line behavioral context. Every sentence earns its place.

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?

The description gives enough context for an agent to select and call the tool for create, update, or delete operations. Per-action prerequisites are already documented in the schema (rule required for create/update, rule_id for update/delete, shield_zone_id for create). It could mention response behavior or change propagation, but that is not critical for tool selection.

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?

Top-level parameter descriptions in the schema cover 100% of parameters, but the nested rule object is opaque with additionalProperties: {}. The description compensates by enumerating the rule object fields such as shieldZoneId, requestsPerSecond, and matchValue. It adds meaningful payload guidance beyond the schema, though it does not explain the semantics of each field.

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 opens with a specific, multi-verb action on a concrete resource: 'Create, update, or delete a rate limit rule.' This clearly distinguishes it from sibling tools such as bunny_list_rate_limit_rules or bunny_manage_waf_custom_rule, which involve different resources or read-only behavior.

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 first sentence makes the tool's intended use clear: call this when an agent needs to mutate a rate limit rule via create, update, or delete. It does not explicitly name alternatives or state when not to use the tool, so it falls short of the strongest guidance, but the mutation scope is immediately obvious from the description.

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