delete_component_folder

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool performs a deletion but doesn't specify whether this is permanent, requires specific permissions, affects nested items, or has rate limits. The description is minimal and lacks critical behavioral context needed for safe operation of a destructive action.

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 extremely concise—a single sentence that directly states the tool's function. It's front-loaded with the core action and resource, with no unnecessary words. Every part of the sentence earns its place by specifying the operation and required 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?

Given this is a destructive operation with no annotations, 0% schema description coverage, and no output schema, the description is incomplete. It doesn't address safety considerations, error conditions, return values, or system impact. For a deletion tool, this level of minimalism creates significant risk for the agent.

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 0%, so the description must compensate. It mentions the parameter 'component_folder_id' and specifies it's used 'by ID', which adds meaning beyond the schema's type declaration. However, it doesn't explain what a component folder ID is, its format, or where to find it, leaving significant gaps in parameter understanding.

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 target resource ('a component folder by ID'), making the purpose immediately understandable. It distinguishes from siblings like 'delete_component' or 'delete_asset_folder' by specifying the resource type. However, it doesn't explicitly mention what 'component folder' means in this context or how it differs from other folder types.

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 doesn't mention prerequisites (e.g., whether the folder must be empty), consequences (e.g., if it's permanent or reversible), or when to choose this over other deletion tools like 'bulk_delete_assets' or 'delete_asset_folder'. The agent must infer usage from the tool name alone.

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