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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the destructive nature is covered structurally. The description adds nothing beyond the raw HTTP endpoint: it does not say whether the folder's contents are also deleted, whether the action is reversible, or what authorization is required.

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 fragments, purpose first, no padding. The REST endpoint line is low-value for an agent but is a compact convention rather than bloat.

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, destructive folder deletion with no output schema and no annotations explaining scope, the description should address cascade behavior and failure modes. Neither is present, leaving a meaningful gap for a high-consequence operation.

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 100% ('Folder ID'), so the single parameter is fully documented in the schema. The description only restates it as a path segment ({id}), adding no format, source, or validation detail. Baseline 3 applies when the schema does the work.

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 (Delete) and a specific resource (CEX signal bot folder), which implicitly separates it from the dex/prediction folder-deletion siblings. It does not name those siblings explicitly or describe what a folder contains, so it falls short of a 5.

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 when-to-use guidance, no prerequisites (e.g., whether the folder must be empty first), and no reference to alternative tools like put_bot_signal_cex_folder_id for renaming. The agent must infer usage purely from the name.

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