delete_folder

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

With no annotations, the description carries the full destructive-operation burden. "Permanently" usefully signals irreversibility, but nothing is said about required permissions, cascade behavior on folder contents, or preconditions such as an empty folder.

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?

A single front-loaded sentence with zero waste. It is efficient, though arguably too terse given the destructive nature and the undocumented parameter.

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?

For an irreversible delete with no annotations and an undocumented required parameter, this is under-specified. The output schema spares it from explaining return values, but permission, cascade, and precondition context are 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?

One parameter with 0% schema description coverage: folder_id is a bare string with no explanation in either schema or description. The description only implies it identifies the target folder, adding no format, scope, or identifier-type detail.

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?

States a specific verb and resource ("Permanently deletes a folder") and locates it in the InfoStore repository, which separates it from siblings like delete_webi_doc, delete_instance, or create_folder. It does not explicitly name the boundary against get_folder_details or create_folder, but the resource 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?

There is no when-to-use guidance, no prerequisites, and no stated alternatives. An agent gets no signal about whether the folder must be empty, what happens to contained documents, or when to prefer a non-destructive sibling.

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