aiwatcher_delete_prompts

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

With no annotations, the description must carry the full burden of behavioral disclosure. It only states 'Delete' without explaining whether deletion is permanent, whether it affects associated monitors, or any side effects. This lack of transparency is a significant gap for a destructive operation.

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 sentence with no filler and front-loads the action. However, its brevity borders on under-specification, so it doesn't earn a 5 for conciseness.

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 lacks annotations, output schema, and specific parameter semantics. The one-line description is grossly insufficient for an agent to correctly invoke the tool, as it doesn't explain endpoints, required identifiers, or side effects.

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's parameter descriptions are generic boilerplate about body/query and do not convey tool-specific meaning. The description does not explain what parameters should be passed to identify which prompts to delete, and with 0 required parameters, the invocation semantics are unclear.

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 uses the verb 'Delete' and identifies the resource 'AI Search Watcher prompts', which clearly distinguishes it from sibling tools like aiwatcher_delete_monitor and aiwatcher_delete_tracking. However, it lacks scope details such as whether it deletes a single prompt, multiple prompts, or all prompts, so it's not fully specific.

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, prerequisites, or alternatives. It doesn't mention related tools like aiwatcher_prompt_detail or aiwatcher_monitor_prompts, leaving the agent without context for selecting this tool.

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