find_listings

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

With no annotations, the description carries the full burden, and it delivers: it discloses the shared 600-search/6h rate budget, states that the server cannot actually send the whisper, explains why (no GGG trade-execution API and ToS), and clarifies that a human must complete the trade. This is exactly the kind of behavioral context agents need beyond the schema.

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 compact, front-loaded with the core purpose, and each additional sentence adds meaningful operational context. There is no filler or repetition of schema-discoverable facts.

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 covers the critical rate budget, alternative tool routing, and whisper-execution constraints, and an output schema exists for return values. The main gap is the absence of parameter semantics, which leaves the agent to rely on names and defaults when constructing a query.

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 input schema has 0% description coverage and the description adds no explanation of the parameters name, type, limit, or league. The parameter names are self-evident to a human, but an agent receives no guidance on what values are valid, how filters combine, or what the limit controls.

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 opens with a specific verb and resource: "Search live trade listings right now, returning prices and whisper text." It clearly identifies what the tool does and distinguishes it from siblings like get_price and search_items by its live, whisper-returning behavior.

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 explicitly tells the agent to "prefer get_price when recorded data is good enough," naming an alternative and the condition for choosing it. It also explains the rate-budget tradeoff and that this tool is the path for obtaining a human-executable trade whisper.

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