project_folder_delete

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

The destructiveHint annotation already signals danger, and the description adds the key behavioral constraint that the folder must be empty. This goes beyond what annotations alone convey, making the tool's behavior more transparent.

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 two short sentences, front-loaded with the action and resource, and every word adds value. No unnecessary details or fluff.

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 simple deletion tool with one fully documented parameter, the description completely covers what an agent needs to know: what it does, where it operates, and a critical precondition. The output schema exists, so return values need not be described.

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?

With schema coverage at 100% and the parameter description 'Name of the folder to delete' being clear, the tool description adds only the context of 'current database folder' which is already in the description. This meets the baseline for high coverage without adding significant extra meaning.

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 starts with a specific verb 'Delete' and clearly identifies the resource: a folder in the current database folder. This distinguishes it from sibling tools like project_folder_create or project_folder_list, and the scope ('current database folder') is explicit.

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 a clear prerequisite: the folder must be empty. This is essential usage guidance, though it does not explicitly mention alternatives or when not to use the tool. Still, the context is unambiguous.

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