Manage Log Action

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

Discloses idempotency by name, specific error behavior (VALIDATION, already_exists, not_found), and dry-run support. Adds substantial context beyond annotations.

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?

Three concise sentences, each adding distinct value: purpose, idempotency/errors, dry-run. No filler.

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?

Covers purpose and error behavior well. Lacks description of success return value, but for a manage tool that is acceptable given 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 has 100% coverage, baseline 3. Description adds meaning: idempotency key for 'name', validation error for missing 'type', and dry-run capability, raising above baseline.

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 'Add or remove a RouterOS logging action target' using specific verb+resource. It distinguishes from sibling tools like list_log_actions which is for listing.

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?

Provides clear purpose for adding/removing logging actions. Does not explicitly exclude alternatives but context from siblings makes differentiation obvious.

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