foundry_delete_folder

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

Annotations already declare destructiveHint=true, so the description doesn't need to repeat that. It adds valuable context by noting that deleteAll also deletes folder contents, which is a key behavioral nuance not present in the schema or annotations. No contradictions.

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 short sentences, front-loaded with the primary action. No filler words. Every word adds value.

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 a destructive tool with a simple schema and no output schema, the description covers the essential behavior. It could mention that deletion is permanent or requires permissions, but the annotations already signal destructiveness. The deleteAll nuance is included, making it complete for its complexity.

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 50%, with userId and clientId described. The description adds meaning for deleteAll, which is otherwise undocumented in the schema. folderId's purpose is obvious from context, and deleteAll's effect is explained. This compensates for the missing schema descriptions.

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 deletes a Foundry folder and specifies the deleteAll parameter behavior. It distinguishes itself from sibling delete tools (e.g., delete_entity, delete_scene) by explicitly targeting folders.

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 implies usage (to delete folders) but does not explicitly state when to use this tool over alternatives or any exclusions. It lacks guidance like 'use for folders only' or comparison with delete_entity, so the context is clear but not fully elaborated.

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