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

With no annotations, the description carries the behavioral burden. It explicitly states this is a cached read refreshed every 20 minutes, and explains the scoring criteria, so an agent can reasonably infer that this is a non-mutating operation that may serve slightly stale data. It does not discuss rate limits or auth, but for a simple read tool this is strong disclosure.

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?

The description is concise and front-loaded with the core resource, then adds selection criteria, refresh frequency, and read behavior. The lane list is long but informative, and every clause contributes useful details.

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 simple read-only list with one optional filter, the description explains what is returned, how it is pre-scored, how fresh it is, and that it is cached. It does not cover output ordering or empty-result behavior, but these are minor gaps for this tool.

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%: the only parameter, 'lane', is documented in the schema as 'Optional lane slug to filter'. The tool description adds no extra parameter-level meaning, but none is needed, so the baseline score of 3 applies.

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 clearly identifies a specific resource: the current pre-scored steal list across tracked lanes. It further defines what qualifies (auctions ≥45% under market and mispriced Buy It Now listings), making the tool's function unambiguous. It does not explicitly differentiate from siblings like scan_deals, but the resource and criteria are specific enough.

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 explicit guidance is given about when to use hot_list instead of sibling tools such as scan_deals, price_check, or flip_margin. 'Fast cached read' and 'current' imply it is for quick snapshots, but there are no clear when-to/when-not-to conditions or alternatives.

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