Delete Saved Search

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

No annotations are provided, so the description carries the full burden of disclosing destructive behavior. It only vaguely says 'confirmation and safety checks' without describing what safety checks occur, whether deletion is reversible, what happens when confirm is false, or what permissions are needed. For a delete operation this is insufficient.

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 short, front-loaded sentence with no filler: 'Delete a saved search with confirmation and safety checks.' It earns its place by identifying the operation, but 'safety checks' is vague and could be replaced with concrete behavior without adding much length.

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 4-parameter destructive tool with no annotations and no output schema, the description is incomplete. It should explain prerequisites, what the confirmation flag does, consequences of deletion, and possibly return behaviors. The vague 'safety checks' does not adequately cover the context needed for a destructive operation.

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%, and the description adds no details about the parameters app, name, owner, or confirm. The only indirect reference is 'confirmation', which loosely maps to confirm, but it does not explain semantics, defaults, required fields, or the roles of app and owner. The description provides no value beyond the schema's raw field names.

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 specific action and resource: 'Delete a saved search'. This distinguishes it from siblings like list_saved_searches, update_saved_search, and create_saved_search. The additional mention of confirmation/safety checks hints at its distinct destructive behavior.

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?

No when-to-use or when-not-to-use guidance is provided. The tool name alone implies it is for deleting saved searches, but the description does not clarify use cases vs alternatives like update_saved_search, list_saved_searches, or create_saved_search. 'With confirmation and safety checks' hints at conditions but does not explain them.

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