netbox_delete_object

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

With no annotations, the description carries the full burden and meets it well. It discloses the most important destructive behavior: deletion is permanent, confirm=True is mandatory, and the operation is disabled when the server is read-only. This is strong transparency for a mutation tool.

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 compact and front-loaded: the critical warnings appear in the first two sentences, and the Args block is lean. Every sentence earns its place without filler or redundant restatement.

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 that an output schema exists and no annotations are provided, the description covers the essential behavior, parameters, and confirmation requirement needed to invoke the tool correctly. It could optionally reference list_endpoints for valid endpoint strings, but nothing necessary for correct invocation is missing.

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 0%, and the description fully compensates by explaining all three parameters: endpoint as an 'app.endpoint' string with a concrete example, id as a numeric ID, and confirm as the explicit safety gate that must be true. It adds real meaning beyond the raw 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?

Opens with a specific action and resource: 'Delete an object from a NetBox endpoint.' 'This is permanent' further pins the destructive semantics, and the verb 'delete' plus the endpoint concept distinguishes it from the list/create/update/schema sibling tools.

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 provides clear operational context—permanent deletion, confirm=True required, and read-only mode disabling—but it does not explicitly name alternatives or state when not to use this tool versus update_object or create_object. Routing to siblings is only implied by the tool's name and purpose.

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