npm_update_redirection_host

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

No annotations are provided, so the description carries the full behavioral burden. It states that it updates a host and supports advanced_config, but does not disclose whether updates are partial or full, what permissions are required, whether changes are reversible, or the risks of custom nginx configuration.

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 two short sentences, with the core purpose front-loaded and no obvious filler. The second sentence about advanced_config is somewhat redundant with the schema but still concise.

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?

This is a mutation tool with 13 parameters, no annotations, and no output schema, yet the description omits critical context such as partial update semantics, permission requirements, and side effects or risks of advanced_config. It provides only the bare minimum purpose statement for a complex update operation.

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%, so the schema already documents all 13 parameters. The description only repeats that advanced_config is supported, adding no syntax, format, or constraint details beyond what the schema provides, which matches the baseline of 3 for high-coverage schemas.

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 gives a clear verb and resource ('Update an existing redirection host'), distinguishing it from create, delete, list, and get operations. It does not explicitly differentiate itself from sibling update tools for other host types, but the resource name itself provides adequate separation.

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?

There is no explicit guidance on when to use this tool versus alternatives, nor any mention of prerequisites such as needing an existing host ID or admin permissions. The phrase 'Update an existing redirection host' implies the usage context but leaves all routing decisions to the agent.

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