shiori_delete_bookmarks

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

No annotations are present. The description only states what the tool does, but not how it behaves—e.g., whether deletion is permanent, if confirmation is required, rate limits, error handling, or side effects. The agent cannot assess risk or side effects from this description.

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, clear sentence that is front-loaded with the action. It is concise and to the point, though it could include more context. It earns its place without redundancy.

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 has one parameter, no annotations, and an output schema (not detailed in description), the description is too minimal. It omits crucial context such as the permanence of deletion, authentication requirements, error behavior, or what the output represents. The agent cannot fully evaluate suitability.

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 single parameter 'ids' is fully described in the input schema with explanation that it accepts an array of integers or a JSON array string. The tool description adds no additional meaning beyond what the schema already provides. With 100% schema coverage, baseline is 3.

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'), the resource ('bookmarks'), and the selection method ('by id'). It distinguishes from sibling tools like shiori_delete_bookmark (singular) by explicitly allowing one or more, and from others like shiori_add_bookmark or shiori_update_bookmark by focusing on 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?

No usage guidelines are provided. The description does not explain when to use this tool versus the singular variant shiori_delete_bookmark, nor does it mention prerequisites, limitations, or when not to use it. The agent is left to infer from the name alone.

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