apidog_delete_api_detail_folder

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

No annotations are provided, so the description must carry the full burden. It discloses the destructive nature ('Delete') and the confirmation requirement, but does not mention permanence, cascading effects, authorization needs, or other behavioral consequences. This is a minimal disclosure for a deletion operation.

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 a single concise sentence, front-loaded with the action and target. Every word contributes value, and it is appropriately sized for a simple deletion tool.

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 simple nature of the tool, the description covers the essential action and confirmation requirement. However, without annotations or an output schema, it leaves out potentially important context such as whether deletion is permanent or affects child resources. It is minimally complete but lacks depth.

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?

The schema provides descriptions for branchId and projectId, but folderId lacks a description. The description adds no direct explanation of folderId beyond the tool name, and repeats the confirmDelete=true requirement already present in the schema via 'const'. With 50% schema coverage, the description only partially compensates.

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') and the target ('API detail folder'), distinguishing it from sibling delete tools like apidog_delete_module or apidog_delete_api_detail. The inclusion of 'Requires confirmDelete=true' provides a precise condition for the operation.

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?

No guidance is provided on when to use this tool versus alternatives. The description only states the action and the confirmDelete requirement, but offers no context about prerequisites, exclusions, or alternative tools.

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