delete_page

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

The description mentions the destructive and irreversible nature ('Permanent — Canvas may retain a recycle-bin copy'), which adds context beyond the annotations (destructiveHint=true, idempotentHint=true). It does not contradict annotations, so transparency score is neutral. It could have warned about authentication requirements or cascading effects, but the note about recycle-bin shows partial transparency.

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 (two sentences) and the most important info (permanence) is front-loaded. Every word is useful.

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 that the tool is a simple delete operation, the description covers the necessary behavior. However, it doesn't mention what happens to associated resources or whether confirmation is required. Since there's no output schema, a note on return values could enhance completeness, but it's not critical.

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 input schema already has high coverage (100%) with clear parameter descriptions ('Page URL slug or page ID to delete', 'Course code or Canvas ID'). The description does not add additional semantics beyond what schema provides, so baseline 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 clearly states the action ('Delete a page') and the resource ('from a Canvas course'). It distinguishes itself from sibling tools like update_page_settings or bulk_update_pages by specifying the destructive action. The additional note about permanence adds important context.

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 does not specify when to use this tool versus alternatives. It doesn't mention that require_title_match can be used as a safety check to avoid accidental deletion, or that alternatives like bulk_delete_pages or soft-delete methods might exist. No exclusions or preconditions are provided.

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