xql_library_delete

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

With no annotations, the description must carry the behavioral burden. It clearly indicates a delete operation and permission requirements, but does not disclose whether deletion is irreversible, mention side effects, or describe the response format. This is a moderate level of transparency.

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 well-organized with a clear heading, short explanation, permission note, endpoint, and example. The only redundancy is the repetition of 'Delete XQL queries' in the first two lines, but overall it is concise and front-loaded.

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?

For a destructive tool with no output schema or annotations, the description provides permission and an example but omits response details, error handling, and clarification of the filter exclusivity. It is usable but not fully complete for an agent to understand all behavioral outcomes.

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 0% for the top-level parameter, so the description must compensate. It explains the two filter options and provides an example. However, the example includes both filters in one request, which contradicts the schema's note that they are mutually exclusive, and it does not clarify whether at least one filter is required.

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 XQL queries' and specifies filtering by query names or tags. This distinguishes it from sibling tools like xql_library_get and xql_delete_dataset, making the purpose unambiguous.

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?

It provides important context by requiring Instance Administrator permissions and includes an example request. However, it does not explicitly contrast with alternatives or state when not to use this tool, so it falls short of full guideline clarity.

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