delete_network

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

No annotations provided, and description doesn't disclose side effects (e.g., irreversibility, cascading deletes) or required permissions beyond the destructive nature implied by 'delete'.

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?

Two sentences, no redundant information. Front-loaded with primary purpose, then guidance. Extremely concise.

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?

With 1 param and no output schema, description covers basics. But lacks behavioral details (e.g., side effects) and fails to compensate for missing annotations, leaving gaps for a destructive operation.

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 already describes the ref parameter with example. Description adds value by specifying the source of the reference ('from get_networks').

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?

Clearly states 'Delete a network from Infoblox IPAM', specific verb and resource. Distinguishes from sibling create_network and get_networks.

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?

Tells agent to get the reference from get_networks first, providing clear prerequisite. No mention of when not to use, but adequate for a simple delete tool.

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