iyke_query_cache

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

The description discloses that it returns a data preview truncated to 200 chars and lists the fields. However, it does not indicate if the operation is read-only or destructive, nor does it explain the effect of the 'pane' parameter. No annotations are provided to compensate.

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?

Two sentences that are front-loaded and contain no unnecessary words. The first sentence lists output contents, the second gives the use case.

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 output fields but omits any explanation of the 'pane' parameter, which is the only input. Without that, the tool is incomplete for the agent to use correctly.

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 has one undocumented parameter 'pane' with no description, and the tool description does not mention it at all. Schema coverage is 0%, so the description fails to explain what this parameter does.

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 TanStack Query cache and lists the fields included (queryKey, status, etc.). It distinguishes itself from sibling diagnostic tools like iyke_state or iyke_logs by being specific to query cache.

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 provides a clear use case: 'diagnosing stale data or failed fetches.' However, it does not explicitly compare to alternative tools or state when not to use it.

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