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

Annotations declare destructiveHint=true and readOnlyHint=false, which is surprising for something called 'Run a saved query', yet the description says nothing about side effects, whether the underlying query may write data, or what permissions are needed. With no annotations-level explanation of the risk, the description's silence on destructiveness is a significant gap (no contradiction, however).

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?

One tight, front-loaded sentence with no filler. It is efficient, though the terseness is partly under-specification rather than deliberate economy.

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?

An output schema exists so return values need not be described, but for a destructive-flagged tool with a nested 'values' object and multiple competing siblings, the description leaves the agent without routing guidance or risk disclosure. It covers the mechanic of variable substitution and nothing else.

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 description coverage is 100%, so id, limit, values, and timeZone are already fully documented, establishing a baseline of 3. The description's mention of variable substitution reinforces the 'values' parameter but adds no syntax or fallback behavior beyond what the schema already says.

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?

States a specific verb and resource ('Run a saved query') plus a distinctive behavior: substituting declared {{variables}} from supplied values. That distinguishes it reasonably from save_query or list_queries, though it never names the nearest sibling, execute_query, so the reader must infer the difference.

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 gives no when-to-use guidance and never mentions alternatives such as execute_query or run_schedule_now, which are the obvious competing entry points. An agent must infer that a saved query id is required and that this is the ad-hoc execution path rather than the scheduled one.

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