delete_folder

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

Without annotations, the description carries full burden. It discloses that deletion requires an id_or_path and returns the id on success or ToolError on failure, but omits critical behavioral traits like whether deletion is recursive, permanent, or requires specific permissions.

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 moderately concise but includes redundant phrasing (e.g., 'If not provided, an error will be returned' is implied by required). Could be shortened without losing 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?

Given the tool's simplicity (one required param, no annotations, output schema exists but not provided), the description is somewhat complete. It explains return values (id or ToolError) but lacks behavioral context such as side effects or authorization needs.

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 description adds meaning beyond the input schema by specifying that id_or_path is a 'unique identifier or path' and that absence causes an error. Schema coverage is 0% (no description in schema), so the description compensates well for this single parameter.

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 it deletes a folder in the content repository via GraphQL API, distinguishing it from siblings like create_folder and update_folder. The verb 'Deletes' and resource 'folder' are specific, but it doesn't clarify deletion semantics (e.g., cascading, irreversibility).

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 on when to use this tool versus alternatives like update_folder or delete_document_version. The description lacks context for appropriate usage scenarios or prerequisites.

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