redash.fetch_query_results

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

Describes polling behavior, fallback on 403, and untrusted data note. With no annotations, it partially covers behavioral traits but omits mutability, auth needs, and rate limits.

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?

Three sentences, front-loaded with core action. Efficient but could benefit from structured lists. No redundancy.

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?

Given 7 parameters, no output schema, and no annotations, the description is too brief. Lacks parameter behaviors, return format, error handling, and prerequisites.

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 coverage is 0%, so description should clarify parameters. Only mentions 'parameters' in passing but offers no details on max_age, max_rows, etc. Fails to add meaning beyond the schema.

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 verb 'Fetch rows' with 'one allowlisted Redash query' clearly states the action and resource. Distinguishes from siblings like get_cached_query_results (cached) and get_query (definition).

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?

Provides context like optional refresh and fallback caching, but no explicit when-to-use vs alternatives or exclusions. Usage is implied but not clearly differentiated from sibling tools.

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