Replace header rules

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

The description explicitly discloses destructive behavior: 'This deletes all existing header rules for the service that aren't included in the request.' This goes beyond the annotation's destructiveHint by specifying exactly what gets deleted. It also mentions the HTTP method, adding transparency.

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?

Three concise sentences: purpose, behavior, and endpoint. Every sentence contributes essential information with no fluff, and critical warning is highlighted prominently.

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?

For a replacement operation with clear destructive semantics, the description is complete. It explains the action, the destructive consequence, and the target endpoint. No output schema exists, so return details are not required, and annotations cover idempotency and destructive nature.

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 100%, and the schema already explains each parameter (body and serviceId). The description adds no additional parameter-level detail beyond what the schema provides, so the baseline of 3 is appropriate.

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?

Clearly states 'Replace header rules' and specifies 'Replace all header rules for a particular service with the provided list', which distinguishes it from siblings like add or delete. The mention of the exact API endpoint reinforces its purpose.

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 clearly implies this is for replacing the entire set of header rules, and the warning about deletion clarifies behavior. However, it does not explicitly name alternatives or exclusions, such as using add_headers for incremental changes, so it falls short of a 5.

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