wdata_run_saved_query

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

No annotations are provided, so the description must fully disclose behavior. It states 'execute' and 'return rows' but fails to mention whether the operation is read-only, has side effects, or how it handles long-running queries (despite a timeout parameter). The output schema exists but is not described.

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 a single sentence that efficiently conveys the core purpose and references a sibling tool. It is concise, though restructuring to separate the parenthetical reference could slightly improve readability.

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 tool has 3 parameters and no annotations, yet the description is too minimal. It does not explain return value format, pagination (max_rows), timeout behavior, or prerequisites. The output schema may cover some details, but the description should provide a high-level overview.

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?

With 0% schema description coverage, the description must explain parameters. It only mentions 'by id' (query_id), leaving timeout and max_rows unexplained. The agent has no guidance on the meaning or impact of these crucial parameters.

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 (execute), resource (saved Wdata query by id), and result (return rows). It references the sibling tool wdata_list_queries to find query ids, distinguishing it from similar tools like wdata_run_sql.

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 implicitly indicates use when you have a saved query id and want to execute it, and references wdata_list_queries to obtain ids. However, it does not explicitly mention when not to use it (e.g., for ad-hoc SQL use wdata_run_sql) or provide alternatives beyond the brief reference.

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