Manage Log Rule

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

The description provides detailed behavioral traits beyond annotations, including idempotency keys (topics+logAction), graceful handling of duplicates/not_found for add/remove, and NOT_FOUND thrown for enable/disable when absent. It also mentions dry-run support.

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?

Two sentences: the first clearly states the tool's purpose and actions, the second adds idempotency details and dry-run. No wasted words.

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?

The description covers all actions, idempotency, error handling, and dry-run. However, it does not specify the output format (e.g., success message or rule ID) since there is no output schema.

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 baseline is 3. The description adds the idempotency key concept for topics and logAction, but otherwise does not add significant meaning beyond the schema.

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 states 'Add, remove, enable, or disable a RouterOS logging rule' with a specific verb and resource, clearly differentiating it from sibling tools like list_log_rules and manage_log_action.

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 explains idempotent behavior and graceful error handling for each action, but does not explicitly state when to use this tool versus alternatives like manage_log_action for managing actions.

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