Manage VRRP Instance

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

Annotations already provide idempotentHint=true. The description adds specific idempotency behavior for 'add' (returns already_exists if duplicate). However, it does not describe return values or behavior for other actions (remove, enable, disable), leaving some gaps.

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: two short sentences totaling 37 words, front-loading the core action and adding one critical behavioral detail. No wasted words.

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 tool with 10 parameters and no output schema, the description covers basic purpose and idempotency for add but omits behavior for other actions, error cases, and return format. Schema descriptions fill some gaps but not all.

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%, so baseline is 3. The description adds value by explaining that the 'name' parameter serves as an idempotency key and that duplicate check includes interface and VRID, enhancing understanding beyond schema.

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 adds, removes, enables, or disables a VRRP instance, which is a specific verb-resource combination. It distinguishes itself from sibling tools like list_vrrp_instances by focusing on mutation actions.

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 manage operations but does not explicitly guide when to use this tool vs alternatives or provide exclusions. It mentions idempotency but no context for choosing actions.

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