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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds only the raw endpoint path, no behavioral context such as pagination, ordering, or folder hierarchy shape. With annotations carrying the safety profile, this is adequate but thin.

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?

One short sentence plus the endpoint. Zero waste, fully front-loaded, nothing an agent must scan past.

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 zero-param read tool with no output schema and safety annotations, the purpose is covered. However, without an output schema the description gives no hint of the return shape (folder list vs tree) or how it relates to the _root and _id variants, leaving real gaps for an agent choosing between four similar folder endpoints.

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?

Zero parameters, so there is nothing to disambiguate and the baseline is 4. The description adds no parameter confusion and schema coverage is 100%.

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 (Get) and resource (all prediction signal bot folders), and the embedded endpoint path confirms the resource scope. It is distinguishable from siblings like get_bot_signal_prediction_folder_root and get_bot_signal_prediction_folder_id, though 'all' does the distinguishing rather than explicit differentiation.

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 versus the closely related get_bot_signal_prediction_folder_root, get_bot_signal_prediction_folder_id, or the per-type cex/dex folder siblings. The agent must infer that this returns the full folder collection and others return roots or single folders.

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