bookshelf_delete_remotepathmapping

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

The annotation already declares destructiveHint=true and readOnlyHint=false, and the description merely repeats this with 'DESTRUCTIVE: this deletes data.' It adds no new behavioral context, such as irreversibility, side effects, or permission requirements. The redundancy provides minimal value.

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 extremely concise: two short sentences that immediately state the action and destructive nature. No unnecessary words or filler. It is well-structured and front-loaded.

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?

The description is minimal and lacks context about what a remotepathmapping is, what the id parameter represents, or any prerequisites. While an output schema exists, the description still fails to adequately explain the tool's operation beyond the action. It is barely adequate for a simple delete tool.

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 has one integer parameter 'id' with no description (0% coverage). The description does not explain what 'id' refers to or how it is used. With no parameter information in the description, the agent lacks guidance on this critical input.

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 remotepathmapping.' This uses a specific verb and resource, distinguishing it from sibling tools like create, update, get, and list. The purpose is immediately clear.

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 implies usage: when you need to delete a remotepathmapping. However, it provides no explicit exclusions or alternatives, nor does it describe prerequisites or when not to use. The context is basic but not absent.

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