enable_safe_mode

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

Annotations only indicate non-destructive and not open-world, but the description adds crucial behavioral details: changes are held in memory, auto-reverted on disconnect, and remain pending until committed. This goes beyond the structured data and gives the agent a clear understanding of the tool's stateful implications.

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 sentence that front-loads the main action ('Activates') and packs essential details (memory, auto-revert, commit) without any wasted words. It is appropriately sized for the tool's complexity.

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?

For a simple activation tool, the description covers the core purpose and the primary safety behavior. However, it omits guidance on the 'device' parameter and does not explicitly connect to sibling tools like commit_safe_mode or rollback_safe_mode, leaving slight gaps for an agent invoking the tool in a broader workflow.

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?

The schema shows a single optional 'device' parameter with zero description coverage, and the tool description does not mention this parameter at all. The agent is left without any guidance on what the parameter represents or how to populate it, so the description fails to compensate for the 0% schema coverage.

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 starts with the specific verb 'Activates' and names the exact resource ('MikroTik Safe Mode'), making the tool's purpose clear. It also distinguishes itself from sibling tools like commit_safe_mode and rollback_safe_mode by explicitly stating it activates the mode, while the 'until committed' clause hints at the associated workflow.

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 when to use the tool: before making changes, with the safety net of auto-revert on disconnect. It does not explicitly name alternatives (e.g., commit_safe_mode or rollback_safe_mode) or provide exclusions, but the context is sufficiently clear for an agent to understand the intended usage.

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