Manage Interface List

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

Annotations already mark the tool as destructive and idempotent. The description adds context beyond that: idempotency is achieved 'by name', and removing a list with members is blocked, with the error surfaced as-is. This provides helpful behavioral details.

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 sentences long, front-loaded with the core action, and every sentence adds unique value: the first defines the purpose, the second explains idempotency and a key constraint.

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 no output schema, the description covers the essential behavior: adding/removing lists, idempotency, and the error case for removal of non-empty lists. It assumes some user knowledge (e.g., what an interface list is) but is otherwise complete for its complexity.

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?

All six parameters are described in the schema with 100% coverage. The description adds only the 'idempotent by name' note for the 'name' parameter, which is a minor addition. Baseline score of 3 is appropriate.

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 or removes an interface list, with a specific verb and resource. It distinguishes from siblings like 'manage_interface_list_member' which handles list members, and 'list_interface_lists' which lists them.

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 indicates the tool is for adding or removing interface lists, which implies when to use it, but it does not explicitly state when not to use it or mention alternatives like 'manage_interface_list_member' for member management.

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