redash.get_cached_query_results

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

No annotations are provided, so the description carries the full burden. It discloses that returned rows are 'untrusted external data' and that no query execution occurs. This is good, but it does not cover what happens if no cache exists or if the query is not allowlisted.

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 consists of two concise sentences with no unnecessary words. It is front-loaded with key action and purpose, and every sentence adds value.

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?

With no output schema, the description minimally covers return values (untrusted rows). It lacks details on error cases or what 'allowlisted' entails. For a simple read tool, it is adequate but not fully complete.

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 coverage is 0%, and the description adds no parameter details. While parameter names like query_id, connection_id, and max_rows are moderately self-explanatory, the description could clarify that connection_id comes from list_connections and that max_rows has a maximum of 10000.

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 specifies the verb 'Read', the resource 'cached rows for one allowlisted Redash query', and explicitly states the tool does not trigger query execution. It distinguishes itself from siblings by focusing on cached data without execution.

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 advises using this tool for reading cached results without execution. It implies an alternative (likely fetch_query_results) for fresh execution but does not explicitly name it. The guideline is clear for the intended use case.

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