Manage Package

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

Beyond annotations (which already mark idempotentHint=true), the description adds the crucial behavioral detail that changes require a reboot to apply. This is a key operational constraint not conveyed by annotations. No contradiction.

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, front-loaded with purpose, followed by essential notes. Every word earns its place. No unnecessary details.

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 toggle tool, the description covers purpose, post-condition (reboot), and idempotency. There is no output schema, so return values are not described, but that's acceptable given the tool's simplicity. Minor gap: no mention of what happens if reboot is not performed.

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 the baseline is 3. The description does not add extra meaning beyond the schema; it only mentions the tool's effect, not parameter details. This is adequate but not exceptional.

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's function: 'Enable or disable a RouterOS package.' This is specific and distinguishes it from other 'manage_*' tools. It also adds critical context (reboot needed, idempotent) that further clarifies its role.

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 explicitly tells when to use this tool and what to do after: 'Changes take effect only after a router reboot — use the reboot tool to apply.' It also clarifies idempotency, meaning it's safe to call multiple times. No alternatives are mentioned, but the tool's specificity makes it clear.

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