drouting_update_rule

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

The only behavioral trait mentioned is the optional trigger of MI dr_reload. No annotations exist, so the description carries full burden. Missing information on side effects, permissions, idempotency, or reversibility.

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, front-loaded sentence with no unnecessary words. However, it is too concise and lacks critical details, so it cannot be a 5.

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?

With 13 parameters, no annotations, and no output schema details, the description is insufficient for an agent to correctly invoke the tool. It omits return values, parameter semantics, and behavioral aspects beyond the basic action.

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%, and the tool description adds no explanation of parameters beyond the schema titles. The description only references ruleid, ignoring other important params like groupid, prefix, gwlist, etc.

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 'Update a dynamic routing rule by ruleid' which specifies the action and resource. However, it does not differentiate from siblings like drouting_add_rule or drouting_update_carrier, which also operate on dynamic routing entities.

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. No prerequisites, contexts, or exclusions are provided.

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