Export Config

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

Annotations already indicate safe behavior (idempotent, non-destructive). The description adds context about inline vs file output and compact mode, but doesn't mention file overwrite behavior or permissions. With annotations, this is adequate.

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 short sentences, no filler. Front-loaded with purpose. Every sentence adds essential information.

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 3 parameters, no required fields, and no output schema, the description covers the main behaviors (inline vs file, compact). Lacks error handling or return format details beyond 'script text', but sufficient for a non-destructive export tool.

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 schema already documents parameters. The description adds value by specifying that file saves as <file>.rsc and that inline returns script text, which enriches the schema's bare explanations.

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 that the tool exports router configuration as a RouterOS script, distinguishes between inline output and file saving, and mentions compact mode. It differentiates from siblings by being the only config export tool.

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 implies usage for exporting config but does not explicitly state when to use this over alternatives like create_backup or other config retrieval methods. No exclusions or alternative tool names are given.

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