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

With no annotations, the description carries the burden of behavioral disclosure. It clearly indicates this is a fast cached read, explains data freshness (refreshed every 30 minutes), and specifies inclusion criteria. It doesn't describe output shape or pagination, but the core behavior is transparent.

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 a single dense sentence that front-loads the purpose and includes only meaningful details: coverage lanes, qualification thresholds, refresh interval, and cache behavior. No filler.

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 one-optional-parameter cached list tool, the description covers scope, data source, freshness, and performance characteristics. Exact lane slug values and output format are not given, but these are minor given the schema and list semantics.

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 schema already describes the lane parameter at 100% coverage, so the baseline is 3. The description adds value by enumerating the tracked lane categories and confirming the parameter filters within those lanes, which goes beyond the schema.

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 states a specific resource ('pre-scored steal list') and the exact criteria that qualify items, making the tool's purpose clear. It doesn't explicitly differentiate from scan_deals, but the curated 'hot list' concept is distinct 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?

The description implies usage for fast cached deal lookups and notes the 30-minute refresh cadence, which suggests when it is appropriate. However, it never names sibling alternatives like scan_deals or states when not to use this tool.

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