Refresh Saved Search Cache

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

The description adds valuable behavioral context beyond annotations: 'triggers server-side recomputation; returns once queued' informs the agent that the call is asynchronous and returns immediately after queuing. Annotations already indicate idempotentHint=true and non-destructive nature; description complements this without contradiction.

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 extremely concise: two sentences front-load the main action and then add a critical behavioral note. No superfluous information.

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?

While the description covers purpose and behavior, it omits parameter details and does not mention return values (though output schema exists). For a simple tool with two parameters, the omission of parameter semantics makes it slightly incomplete.

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 has 0% description coverage and the description provides no explanation of the two parameters ('search_id' and 'request_id'). This leaves the agent without guidance on what each parameter represents, which is a significant gap.

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 action ('force a re-cache'), the resource ('saved device search results'), and the condition ('when they may be stale'). It distinguishes from similar tools like 'run_saved_search' or 'get_cached_search_results' by specifying forced recomputation.

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 'when they may be stale' but does not explicitly state when not to use or provide alternative tools. The context is clear but lacks full guidance on selection.

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