Manage Script

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

Discloses idempotency (matches idempotentHint), dry-run capability, and error throwing (CONFLICT, NOT_FOUND). ConfirmationToken description highlights destructive nature (matches destructiveHint). Adds nuance 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?

Two sentences plus compact points. No wasted words. Information front-loaded and easy to parse.

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 core operations, error handling, idempotency, dry-run, and destructive confirmation. With 8 parameters and no output schema, explanation is sufficient for an agent to use correctly.

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 coverage is 100%, so baseline 3. Description adds meaning by linking name parameter to idempotency and dryRun to preview, but does not explain all parameters. Still adds value.

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?

Clearly states the tool adds, updates, or removes RouterOS scripts. Distinct from siblings like run_script or list_scripts. Specific verb+resource with error cases.

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?

Describes idempotency by name and error behavior for add/update. Supports dry-run for preview. Could mention when to use alternatives like run_script, but the scope is clear enough.

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