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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), but the description adds genuinely useful behavioral context: the data is a delayed free sample (one market day), the buy score is banded rather than numeric, and the list may not be actionable at all depending on regime mode. This goes meaningfully beyond the structured fields.

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?

Front-loaded with the core purpose and dense but largely information-bearing, with the free-sample limitations placed last. It reads as a long run-on sentence, which slightly hurts scanability, but almost every clause adds distinct detail about the payload.

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 return-value burden and does so well, enumerating picks per lane, top-3 READY candidates, buy band, entry window, ladder permission, regime mode, and READY count. The only gap is mild ambiguity around how the 'two lanes' relate to the crypto book mentioned parenthetically.

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 zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate. Schema coverage is 100% and no input semantics are needed.

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 names a specific resource (today's ranked buy-list) and details its scope precisely: two lanes, per-book picks, READY candidates, buy bands, entry windows, and regime mode. It implicitly distinguishes itself from get_buy_list_live via the 'free sample / one market day delayed' framing, but never names the sibling explicitly.

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?

The description explains what the tool returns but says nothing about when to use it versus alternatives. The 'free sample' and 'one market day delayed' clues hint at a premium/live counterpart, but the agent is left to infer this and no alternative tool is named.

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