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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered by structured data. The description only adds the underlying endpoint (GET /api/v2/bot/signal/prediction), and says nothing about pagination, result size, ordering, or how complete the 'all' result is — which is meaningful for a list endpoint.

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 clauses, front-loaded with the purpose and then the endpoint. No filler, though the second clause is closer to an implementation detail than agent-facing guidance.

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?

With no output schema, the description carries the burden of indicating what comes back, but it says only 'all'. There are no params or annotations gaps to compensate for, so it is minimally adequate, but an agent still cannot tell whether the list is paginated, ordered, or filtered.

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 has zero parameters and schema description coverage is 100%, so there is nothing for the description to clarify. Baseline 4 applies for a parameterless tool.

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 all prediction signal bots'), which implies a list of prediction signal bots and distinguishes it from the singular get_bot_signal_prediction_id. It does not explicitly name sibling alternatives such as get_bot_signal_prediction_folder or _total, but the 'all' scope makes the intent readable.

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?

There is no when-to-use guidance: it does not say how this differs from get_bot_signal_prediction_id, get_bot_signal_prediction_folder, _folder_root, _market_exchange_slug, or _total beyond the implied 'all'. No prerequisites, no exclusions, no routing advice.

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