delete_directory_line

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

No annotations are provided, so the description must disclose behavioral traits. It correctly identifies this as a user-confirmation-required action and explains the two-step process. The permanent nature of deletion is noted in the schema for id_instance, but the description itself could mention it. Overall, it adds significant 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 extremely concise: two sentences covering the action and the user-confirmation workflow. No unnecessary words, and the critical guidance is front-loaded.

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's complexity (delete with confirmation) and the presence of an output schema (context signal), the description is largely complete. It explains the required workflow. It could add a note about what the summary contains, but the output schema likely covers return values.

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 extra information about parameters beyond what the schema already provides. The schema itself includes descriptions and warnings, so the tool definition is adequate without redundance.

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's purpose: 'Delete a directory line'. It also specifies the HTTP DELETE endpoint, making the action unambiguous. The name and description together distinguish it from sibling tools like update_directory_line and create_directory_line.

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 explicit usage instructions: requires user confirmation, call without confirmation_token first, then call again with the token. It does not explicitly contrast with alternatives, but the context of deletion is clear among siblings.

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