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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safe read-only nature is covered. The description adds only the underlying REST endpoint, disclosing nothing extra about return format, auth, or edge cases; with a count tool this is minor, but the description contributes little beyond annotations.

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 sentences, front-loaded with the purpose. The trailing REST path is marginally useful reference but adds little for an agent; still, nothing is bloated.

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-parameter count tool with no output schema and full annotation coverage, the description is adequate: it says what is counted and that the result is a total. It could note whether the total is workspace-scoped or global, but the core is complete.

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 tool takes no parameters, so the baseline is 4. There is no parameter semantics to clarify and the description correctly implies a global unfiltered total.

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+resource ('Get the total number of CEX signal bots'), which is clear and unambiguous. It does not explicitly differentiate itself from sibling aggregators like get_bot_signal_dex_total or get_bot_signal_prediction_total, but the 'CEX' scope is self-evident from the name and description.

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?

Usage is implied: call it to obtain a count of CEX signal bots, distinct from get_bot_signal_cex which lists them. There is no explicit when-to-use/when-not statement or named alternative, so guidance is inferable but not stated.

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