create_export

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

The description says it 'creates a configuration export file', implying a write/side-effect, but the annotations declare readOnlyHint=true and idempotentHint=true. This is a direct contradiction; creating a file on the device modifies filesystem state. The description fails to disclose behavioral traits beyond what annotations claim, and actively conflicts with them.

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 a single concise sentence with no unnecessary words. It front-loads the key purpose and formats, earning its place despite being terse.

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?

With 8 parameters, 0% schema coverage, and no output description, the tool is under-specified for an agent to use correctly. The description provides minimal context about behavior, return values, or side effects, and does not compensate for the lack of parameter details.

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% with 8 parameters, and the description does not mention any parameters or their semantics. It only lists output formats, leaving the agent to guess what 'name', 'device', 'compact', 'verbose', 'export_type', 'file_format', and 'hide_sensitive' control.

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 the tool creates a configuration export file with specific formats (rsc/json/xml) on the MikroTik device. It is specific about the resource and action, but does not explicitly differentiate from sibling tools like create_backup or export_section, though the format list provides some distinction.

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?

There is no guidance on when to use this tool versus alternatives such as create_backup or export_section. The description only states what it does, leaving the agent to infer when it should be chosen from a large set of related tools.

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