Manage VRRP Instance

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

Annotations already convey destructiveHint and idempotentHint. The description adds value by explaining the idempotency behavior for 'add' (returns already_exists). However, it does not disclose other behavioral traits such as how enable/disable work, whether they are idempotent, or side effects beyond that.

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 two concise sentences: the first lists all actions, the second explains idempotency behavior. It is front-loaded and contains no superfluous information.

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?

Given the tool has 11 parameters, destructive behavior, and no output schema, the description is incomplete. It does not cover expected return values, error scenarios (e.g., what happens if remove is called on a non-existent instance), or when the confirmationToken is needed. The agent lacks enough context to use the tool correctly in all scenarios.

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 additional semantic meaning to parameters beyond what is in the schema. It mentions 'name' as idempotency key but that is already in the 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 handles four specific actions (add, remove, enable, disable) on a VRRP instance and distinguishes it from siblings like list_vrrp_instances. The idempotency behavior for 'add' is explicitly described.

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 hints at usage by listing actions but does not explicitly guide the agent on when to use this tool versus alternatives. For example, it does not mention that 'list_vrrp_instances' should be used for listing. The idempotency note provides some context but no overall usage guidance.

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