Delete Fhrp_group

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

The description goes well beyond annotations by detailing cascading deletes with concrete examples and stating irreversibility. It also mentions the HTTP 204 response, providing full behavioral context.

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 concise and well-structured: a purpose line, a warning paragraph with bullet-like clarity, and a return statement. Every sentence adds value.

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?

The description covers the destructive nature and confirmation requirement well. However, it could mention that the id must first be obtained via netbox_get_fhrp_group or netbox_list_fhrp_groups to complete the workflow context.

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?

With 100% schema coverage and a single parameter described in the schema as 'Numeric id of the fhrp_group to delete', the description adds only 'by numeric id' which is redundant. It does not provide additional semantics beyond 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 action (Delete), the resource (fhrp_group), and the method (by numeric id). It distinguishes this tool from siblings by its specific resource, and the use of 'fhrp_group' is unambiguous.

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 instructs confirming with the user before calling due to destructiveness, but it does not compare with other delete tools or specify when to use this versus related tools like netbox_delete_fhrp_group_assignment.

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