delete_queries

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

The description does not disclose any behavioral traits beyond the fact that it deletes multiple queries. With no annotations provided, critical information such as irreversibility, permission requirements, side effects on dependent resources (e.g., pages using queries), or error handling is missing.

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, clear sentence with no filler words. It is concise and front-loaded, effectively communicating the core action.

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 the tool's destructive nature and lack of output schema, the description is insufficient. It does not explain return values, success/failure signals, or how deletion fits into the broader app lifecycle (e.g., impact on pages that reference deleted queries).

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 0% description coverage for its single parameter 'query_ids'. The description only implies that query_ids are the identifiers of queries to delete, but does not explain the expected format, origin (e.g., from list_queries), or any constraints like minimum or maximum count.

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 verb 'delete' and the resource 'queries', and emphasizes 'multiple queries in one tool call', which distinguishes it from other delete tools for different resources (e.g., delete_app, delete_datasources) and from query-related tools like execute_queries or update_queries.

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 no guidance on when to use this tool versus alternatives (e.g., updating queries to disable them, or using list_queries to review before deletion). No conditions or exclusions are mentioned.

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