delete_announcements_by_criteria

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

The annotations already flag destructiveHint=true and idempotentHint=false, so the description's statement that deletion is 'Permanent' adds meaningful context beyond the structured annotation. It also mentions the nuance that Canvas may retain a recycle-bin copy depending on admin settings, which is a helpful behavioral caveat.

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 two short sentences and is immediately front-loaded with the core action. The second sentence adds relevant destructiveness context without padding or unnecessary detail.

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?

With a destructive multi-parameter tool and no output schema, the description is adequate but not fully complete: it conveys permanence and criteria-based selection, while the schema covers parameters. Missing context includes when to prefer this over sibling delete tools and what the tool returns or does on dry_run, so the overall description is acceptable but has clear gaps.

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 100%, so the input schema already documents all four parameters including criteria keys, limit, and dry_run. The description does not add parameter-level semantics beyond saying 'specific criteria,' so the baseline of 3 is appropriate.

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 states a clear action ('Delete announcements') and a specific selection mechanism ('matching specific criteria'), so the tool's purpose is obvious. However, it does not explicitly differentiate itself from the sibling tools delete_announcement, bulk_delete_announcements, or delete_announcement_with_confirmation; the distinction is mostly left to the tool name.

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 gives no guidance on when to use this tool versus alternatives such as delete_announcement or bulk_delete_announcements, and it does not mention any prerequisites or exclusions. The only implied usage is that it operates on multiple announcements by criteria, which is also apparent from the tool name.

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