Replace header rules

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

The description clearly states that it deletes existing header rules not in the request, which is destructive behavior. However, the annotations set 'destructiveHint' to false, creating a contradiction. Per scoring rules, score 1 for contradiction.

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, with the key behavior and API call front-loaded. It is fairly concise, though the first sentence repeats the title. Could be slightly more efficient.

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 no output schema, the description explains the replacement effect and deletion of omitted rules. It mentions the API endpoint. It could mention prerequisites like service existence or permissions, but it covers the main behavioral context adequately.

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 baseline is 3. The description does not add significant meaning beyond the schema; it only mentions 'the provided list' and 'serviceId' without additional detail.

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 verb 'Replace' and the resource 'header rules for a particular service'. It distinguishes from siblings like 'render_add_headers' (adds) and 'render_delete_header' (deletes one) by specifying that it replaces all rules.

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 explicitly warns that this operation deletes all existing header rules not included in the request, guiding when to use it vs alternatives. It could be improved by adding explicit 'use this when you want to completely replace, not when you want to add or delete individual headers'.

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