Manage Bridge Port

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

The description adds idempotency information beyond annotations, stating 'Idempotent: add returns already_exists if the port assignment already exists.' This is valuable. Annotations already provide destructiveHint and idempotentHint, so the description complements them without 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?

The description is extremely concise at two sentences, front-loading the core action and adding the idempotency detail. Every word serves a purpose with no redundancy.

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?

No output schema exists, and the description does not explain return values or error conditions beyond the idempotency note. For a destructive tool (destructiveHint true), more details on confirmationToken usage or removal behavior would improve completeness. It is adequate but not comprehensive.

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%, and the description does not elaborate on parameters beyond their basic schema definitions. Parameters like dryRun and confirmationToken are described in the schema but not in the description; the description meets the baseline but adds no extra semantic 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?

The description clearly states the verb and resource: 'Add or remove an interface from a bridge on a MikroTik router.' It distinguishes this tool from siblings like manage_bridge (which manages the bridge itself) and list_bridges, as it specifically deals with port membership.

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 adding or removing bridge ports but does not explicitly state when to use this tool versus alternatives like manage_bridge or list_bridges. However, the context signals show many sibling tools, and the purpose is clear enough to infer appropriate use cases.

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