Remove Bookmark

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

Annotations are absent, so the description owns the burden. It discloses that the operation is a DELETE via POST, but does not mention side effects like irreversibility, authentication requirements, or what happens if the bookmark does not exist. The single sentence is thin on behavioral context beyond the endpoint.

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 a single concise sentence that names the action and the endpoint. It front-loads the purpose ('Remove a CivitAI bookmark') and includes the HTTP method and path, with zero wasted words.

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 simple one-parameter tool, the description is minimal but lacks any usage context, error behavior, or idempotency notes. It is adequate for basic understanding but does not fully equip the agent to use it correctly in all situations (e.g., what happens if the bookmark doesn't exist).

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 schema describes the only parameter 'name' fully ('Bookmark name to remove'), and coverage is 100%. The description adds no extra semantics beyond what the schema already provides, so it meets the baseline but does not enhance understanding.

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 it removes a CivitAI bookmark, uses a specific verb (Remove) and resource (bookmark), and indicates the HTTP endpoint. It distinguishes itself from sibling tools like sdnext_civitai_add_bookmark and sdnext_civitai_remove_banned by naming the exact resource type.

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 on when to use this tool versus alternatives, no prerequisites, and no mention of when not to use it. It only states the action without any context for selection, so the agent has to infer based on the name.

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