get_request_header_rules

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

There are no annotations, so the description carries full responsibility for behavioral disclosure. 'Get' indicates a read-only operation, but the description does not mention what is returned, whether pagination is involved, or how missing/empty rules are handled. It is adequate for a simple getter 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?

The description is a single sentence with no filler or redundancy. It front-loads the action and clearly names the resource and scope.

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 tool is simple, with one well-documented parameter and no output schema, so the minimal description is mostly sufficient. However, it lacks any indication of the return shape or usage context, and there is no guidance to steer an agent away from similar sibling tools.

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 single parameter zone_id is fully documented in the input schema with a clear description ('The zone ID'). The tool description adds no extra parameter semantics beyond identifying the zone scope, so the schema already carries the load.

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 identifies the action ('Get'), the resource ('HTTP request header modification rules'), and the scope ('for a zone'). The 'request header' phrasing distinguishes it from the sibling get_response_header_rules and similar rule-list tools.

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?

No guidance is provided about when to use this tool instead of related tools like get_response_header_rules, get_url_rewrite_rules, or get_origin_rules. The intended use is only implied by the name and the phrase 'for a zone'.

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