bulk_delete_announcements

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

Annotations already mark destructiveHint=true. The description adds behavioral details: permanent deletion with possible recycle-bin, dry_run behavior that fetches titles without deleting, and limits ignored when dry_run=True. This provides useful context beyond annotations.

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 well-structured with a summary line, a permanence note, and an Args list. It is concise but not terse; every sentence adds value. A minor improvement would be removing the 'Args:' header since it's a docstring convention, but overall effective.

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?

Given 5 parameters and an existing output schema, the description covers parameter behavior comprehensively. It does not describe the output, but that is handled by the output schema. The dry_run and limit details ensure safe usage. Slightly more context on error behavior could boost completeness.

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 0% (no descriptions in input schema). The description fully compensates with an Args block explaining each parameter: course_identifier, announcement_ids, stop_on_error, limit, and dry_run. It clarifies limit ignored when dry_run=True, adding semantics missing from schema.

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 starts with a specific verb+resource 'Delete multiple announcements from a Canvas course.' It clearly distinguishes from single-delete sibling tools like 'delete_announcement' and criteria-based 'delete_announcements_by_criteria.'

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 usage context (permanence, dry_run) but does not explicitly compare with alternative delete tools or state when to use this over siblings. The dry_run parameter is a safety guideline, but no exclusions or when-not-to-use advice is provided.

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