drouting_update_gateway

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

No annotations are provided, so description should disclose behavioral traits. It states 'update' implying mutation, but does not mention side effects, permissions, or the impact of parameters like 'reload'. Lacks behavioral context.

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?

Extremely concise (one sentence), but underinformative. Front-loaded with purpose, but lacks necessary details for parameter understanding and usage. Conciseness comes at cost of completeness.

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 the complexity (11 parameters, no schema descriptions, no annotations), the description is severely incomplete. An agent cannot correctly use this tool without guessing parameter meanings or behavior.

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 0%, so description must add meaning. It only mentions 'gwid', leaving the other 10 parameters (address, type, strip, etc.) unexplained. No value added beyond the schema's basic types.

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?

Description clearly states the action ('Update'), resource ('dynamic routing gateway'), and key identifier ('by gwid'), distinguishing it from sibling tools like drouting_add_gateway and drouting_delete_gateway.

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 on when to use this tool versus alternatives, nor any when-not or context regarding prerequisites or conditions. The description is purely operational.

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