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

With no annotations, the description carries the full behavioral burden. It discloses that the tool performs no new Bazaar search, is free, operates on the in-memory cache, has constraints, and may be empty. It could go further by describing the output shape or side effects, but 'dump' plus the cache semantics make the read-only behavior clear.

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 dense but well-structured: it front-loads the core behavior, then gives precise sibling comparisons and a fallback action. Every sentence adds value and there is no redundant restatement of the tool name or title.

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 zero-parameter list tool with no output schema, the description covers the essential context: what data is returned, what constraints apply, how it differs from siblings, and what to do when the cache is empty. It does not define 'Base' or 'MAX_PRICE_USD', but these appear to be domain constants, and the guidance is sufficiently actionable.

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 has zero parameters, so the empty schema is fully covered. The description adds useful context about the fixed filters applied to the returned cache entries (Base, ≤ MAX_PRICE_USD), which the schema cannot express. This is solid for a parameterless tool.

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 states the tool dumps the in-memory discovery cache with explicit constraints (Base, ≤ MAX_PRICE_USD), and distinguishes it from search_bazaar, quote_route, and list_verified_apis. The verb 'dump' and resource 'in-memory discovery cache' make the action and scope unambiguous.

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 gives explicit when-to-use guidance: prefer this over search_bazaar/quote_route when only warmed cache data is needed, prefer over list_verified_apis when non-Verified cached APIs are desired, and call search_bazaar first if the cache is empty. This fully routes the agent among siblings.

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