search_hot_tools

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

With no annotations provided, the description carries the burden of behavioral disclosure. It clearly states the key behavior of skipping cold tools and defines hot/warm tools. It does not mention side effects, but for a search tool, read-only behavior is implied. The added context about frequency categories goes beyond the name.

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 brief, well-structured paragraph. It first states the purpose, then explains the scope and definitions, with no redundant sentences or 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?

The description is complete for a search tool with an output schema: it clearly defines the filtering scope and motivation. It could be slightly more explicit about the relationship to the sibling 'search_tools', but the 'only' phrasing already communicates that it is a subset.

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% because all three parameters have descriptions. The tool description does not add any additional parameter-level meaning, so the baseline 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 states 'quick search hot tools' and explicitly defines that it only searches hot and warm tools while skipping cold tools. This clearly distinguishes it from the sibling 'search_tools' tool by specifying the scope and performance motivation.

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 that this tool is for performance optimization by skipping cold tools, which implies it should be used when you only need hot/warm tools. However, it does not explicitly name the alternative 'search_tools' for full searches, so there is clear context but no explicit exclusion.

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