canvas_bookmark_delete

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the action is destructive ('Delete', 'Remove'), implying mutation, but lacks details on permissions, reversibility, error handling, or response format. This is inadequate for a mutation tool without annotation support.

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 brief and front-loaded with the core action, using two concise sentences. However, the second sentence ('Remove a bookmark from your list.') is somewhat redundant with the first, slightly reducing efficiency without adding new information.

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 the tool's destructive nature (implied by 'Delete'), lack of annotations, and no output schema, the description is incomplete. It should address behavioral aspects like permissions or consequences, and provide more context for safe usage, especially compared to sibling tools.

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%, with the parameter 'bookmark_id' fully documented in the schema. The description doesn't add any semantic details beyond what's in the schema (e.g., how to obtain the ID), so it meets the baseline of 3 where the schema does the heavy lifting.

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', 'Remove') and resource ('bookmark'), making the purpose unambiguous. However, it doesn't differentiate from sibling tools like canvas_bookmark_create or canvas_bookmark_list, which would require mentioning it's specifically for deletion rather than creation or listing.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing bookmark ID), exclusions, or refer to sibling tools like canvas_bookmark_list for obtaining IDs, leaving usage context unclear.

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