delete_announcements_by_criteria

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

Beyond the destructiveHint annotation, the description adds detail about permanence and potential recycle-bin retention depending on admin settings. It also highlights the dry_run default (True) as a safety mechanism, which is valuable behavioral context not captured by annotations alone.

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 concise, uses clear section headers, and front-loads the core purpose. Each sentence adds value, and the bulleted Args list improves readability without unnecessary verbosity.

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 criteria-based deletion tool with output schema and good annotations, the description covers key behaviors (permanence, dry run) and parameters. It could include potential error conditions or limit behavior, but is sufficiently complete for most use cases.

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?

With 0% schema description coverage, the description fully compensates by explaining each parameter: course_identifier (course code or ID), criteria (dict with specific keys like title_contains, older_than, etc.), limit (safety max), and dry_run (preview mode). This adds crucial meaning beyond the raw schema types.

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 action ('Delete announcements matching specific criteria') and the resource ('announcements'). It distinguishes itself from siblings like 'delete_announcement' (single) and 'bulk_delete_announcements' (bulk without criteria) by specifying criteria-based deletion.

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 includes a note about permanence and recycling, and mentions the dry_run safety feature, but does not explicitly guide when to use this tool over similar siblings like 'delete_announcement' or 'bulk_delete_announcements'. Provides some context but lacks direct comparative guidance.

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