scheduled_queries_delete

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

With no annotations provided, the description carries the transparency burden. It discloses the permission requirement and shows an example, but doesn't state whether deletion is permanent, irreversible, or what happens to scheduled queries with invalid IDs. The example hints at batch deletion but more behavioral details would be useful.

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 reasonably concise, with a minor repetition of 'Delete a scheduled query' and 'Delete scheduled queries'. It effectively front-loads the purpose, then provides permission, endpoint, and example. The structure is clean and each section 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?

The tool is simple, but without an output schema or annotations, the description omits information about return values, error handling, or side effects. The permission note and example provide useful context, but a more complete description would mention the response format or irreversible nature of the delete.

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 only one parameter (request_data) with 0% description coverage. The description compensates with an example showing an array of IDs, implying the parameter is a list of scheduled query identifiers. However, it doesn't explicitly define the format or semantics beyond the example, leaving some ambiguity.

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 'Delete a scheduled query' and 'Delete scheduled queries', identifying the specific action and resource. It distinguishes from sibling tools like scheduled_queries_list and scheduled_queries_insert by focusing on the deletion operation.

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 context for use by stating the permission requirement ('Instance Administrator') and showing the endpoint. It doesn't explicitly mention when not to use or alternatives, but the usage context is clear enough for an AI agent to infer when to invoke it.

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