peaka_delete_query

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

The annotations already declare destructiveHint=true and readOnlyHint=false, and the description merely restates the delete action without adding behavioral detail such as permanence, cascading effects, or confirmation requirements. It adds workflow information, but not meaningful behavioral context beyond what annotations provide.

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?

Two compact sentences with no filler. The action is stated first, followed by the parameter acquisition workflow; every sentence performs a necessary function.

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 simple two-parameter destructive action with no output schema, the description covers both parameters and the prerequisite lookup calls. It could mention irreversibility or visible side effects, but the destructiveHint annotation already signals risk, and nothing critical to invoking the tool is missing.

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 coverage is 100% and both parameters are documented, but the description adds valuable sourcing semantics: queryId is obtained from peaka_list_queries and projectId requires peaka_list_projects plus user confirmation. This goes beyond the bare schema descriptions.

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 ('Delete'), a specific resource ('saved query'), and the target system ('Peaka project'). This distinguishes it from sibling delete tools like peaka_delete_cache and peaka_delete_semantic_table by naming the exact resource type.

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?

Gives explicit workflow guidance: obtain the queryId from peaka_list_queries, and if projectId is unknown, call peaka_list_projects and ask the user which project to use. It does not enumerate alternatives/exclusions, but the context is unambiguous and actionable.

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