bookshelf_delete_metadata

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

The annotations already declare destructiveHint=true and readOnlyHint=false. The description only repeats this via 'DESTRUCTIVE: this deletes data,' adding no new behavioral context such as irreversibility, required permissions, or effects on related entities.

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 very short—two sentences—and front-loads the core action. However, the second sentence is redundant with the destructiveHint annotation, and there is no structured elaboration or additional useful details.

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 destructive operation, the description is minimally sufficient but leaves gaps: it does not clarify what 'metadata' refers to, what the 'id' signifies, or any constraints on deletion. The output schema exists but the description doesn't mention return values, and no further context is provided.

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 has one parameter 'id' with no description (0% schema coverage). The tool description does not explain the meaning, format, or use of this parameter, so the description fails to compensate for the schema's lack of information.

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 states 'Delete metadata' with a clear verb (delete) and resource (metadata). It is distinguishable from sibling delete tools by the resource name, but lacks specificity about what metadata is or any scope.

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. There is no mention of prerequisites, contexts, or related tools like update_metadata or get_metadata.

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