drouting_add_rule

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

Annotations are absent, so the description must disclose behavior. It mentions the optional MI dr_reload trigger (a side effect) but fails to cover prerequisites, authorization, or whether the operation is idempotent. For a mutation tool, this is insufficient.

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 short and front-loaded, wasting no words. However, it is arguably too concise, missing critical details. Still, it earns a 4 given the lack of verbosity.

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 tool's complexity (12 parameters, 3 required, mutation, output schema present), the description is incomplete. It does not explain return values, conflict handling, or the effect of the 'reload' parameter, relying solely on the schema which lacks descriptions.

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 description adds no explanation for any of the 12 parameters. Parameter names like 'sort_alg', 'timerec', and 'attrs' are not self-explanatory, leaving the agent without guidance on their meaning or format.

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 'Add a new dynamic routing rule' with a specific verb and resource. It distinguishes from sibling tools like drouting_add_carrier or drouting_add_gateway, which operate on different entities within dynamic routing.

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 alternative tools such as drouting_update_rule or drouting_add_carrier. The description only mentions an optional reload trigger, not when this tool is appropriate.

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